do not use psycopg2-binary ?

[vincentsarago]

The doc advise to no use the binary as application dependency 🤷‍♂️

The psycopg2-binary package is meant for beginners to start playing with Python and PostgreSQL without the need to meet the build requirements.

If you are the maintainer of a published package depending on psycopg2 you shouldn’t use psycopg2-binary as a module dependency. For production use you are advised to use the source distribution.

ref: https://www.psycopg.org/docs/install.html#quick-install (edit)

https://github.com/arturo-ai/arturo-stac-api/blob/7d4c9572981e935de2521441878f3ffb78f6b9b7/setup.py#L15

[kylebarron]

Can you link to that doc? Do they give any reasons why you shouldn't use the wheel?

[vincentsarago]

@kylebarron updated the issue with the link

I think the main reason is

The binary packages come with their own versions of a few C libraries, among which libpq and libssl, which will be used regardless of other libraries available on the client: upgrading the system libraries will not upgrade the libraries used by psycopg2. Please build psycopg2 from source if you want to maintain binary upgradeability.

[kylebarron]

Since we use Docker it likely isn't an issue. you just need libpq I think.