On Wed, 23 Apr 2025 at 13:24, Devrim Gündüz <dev...@gunduz.org> wrote: > psycopg is included in RHEL 8, but PGDG packages are up2date (2.7.5 vs > 2.9.5) so they override OS packages. That is why things will break. > > A solution would be creating our own psycopg2 (likely for Python 3.12) > package, update all PGDG packages that depend on psycopg2 to use that > package. That is not impossible (I have already psycopg2 built against > Python 3.11 on SLES 15), but I don't know how much work it will be and > its impact as that set of update should go to both RHEL 8, 9 and 10 > (RHEL 10 already includes Python 3.12 by default)
Thanks for that explanation, now I understand the problem. > I can go for this solution if it is *absolutely* required. We already > have custom packages to support PostGIS, so that is not a new topic for > me. I don't really think this would be required to bump Postgres its minimum supported postgres version. psycopg is a client and postgresql is the server, it seems fine for them to use different Python versions. The postgresql-server package could depend on python3.9, while psycopg packages would happily use python3.6.
