> that is indeed stale, thanks for spotting that. The problem is present
> in the other distributions as well. I have now manually updated
> bionic-pgdg, but I will leave the other untouched until I can figure
Thanks!, I've confirmed that my repro no longer works and version 11 is installed.
> That said, you shouldn't worry about libpq5 11 - using the 13 version
> from the "main" repository component is the recommended way.
For my own understanding, what are the ramifications of using the non-"main" repository component / what are the differences?
I was also under the impression that since the version number tracks the postgres release it is compatible with, that I should be choosing the version that matches the version of postgres I'm running, i.e. since I'm running Postgres 11, I should be using libpq5-11.xx. I'm primarily installing libpq for python; however, taking a closer look at psycopg2 docs (
https://www.psycopg.org/docs/install.html#runtime-requirements), I see that they are in agreement with what you're saying:
> Note: Whatever version of libpq psycopg2 is compiled with, it will
> be possible to connect to PostgreSQL servers of any supported
> version: just install the most recent libpq version or the most
> practical, without trying to match it to the version of the
> PostgreSQL server you will have to connect to.
Out of curiosity, if we were running libpq5-11 with Postgres 13, would we see any issues or does postgres maintain backwards compatibility with these libs as well?