I was wondering when it was going to be an issue where something in the
common repo had a postgesql version dependency.
I guess I would argue that if there is a dependency on a particluar
version of postgresql libraries that it should NOT be in a repository
that may not include that postgresql version.
What happens if I need to use PostgreSQL 11 right now (even on the
client side) and still want to use the PyGreSQL package. The yum update
mechanism will pull in the latest PyGreSQL package and everything would
be broken.
It's a little bit of a mess. This PyGreSQL package burned me recently by
changing to python3 which was not on my host. Of course yum dependency
did the right thing and installed the dependent python3 components, but
all of my python code was python2 which no longer had a PyGreSQL
library. But that is a different story.
The only solutions I see are
1. Have the pgdg create other repos for common-pg10, common-pg11 etc
that would contain the common code that has version dependencies. A new
common package would have to go into multiple repos then. A lot of work.
2. The package name changes to include a postgresql version dependent
number such as PyGreSQL12 which would mean that the PyGreSQL11 package
would not get automatically updated. This is in-line with the package
names that the postgresql repos use.
3. Add the package to the portgresql version specific repose rather than
the common repo so that the dependency will be more tightly tied to the
repo that is in use.
As you say, most of this is under the control of the build team, so I
will follow up with them.
Thanks,
On 5/6/21 11:04 AM, Justin Pryzby wrote:
On Thu, May 06, 2021 at 10:35:20AM -0700, Evan Rempel wrote:
repository:
https://download.postgresql.org/pub/repos/yum/common/redhat/rhel-7-x86_64/
That's built by Devrim et al (copied) and not by the pygres team.
Previous builds of the PyGreSQL had an rpm requires list that included only
libpq.so.5()(64bit)
The latest build contains a requires list of
libpq.so.5()(64bit)
libpq5
The inclusion of the libpq5 requirement forces the install of the
pgdg-common package libpq5 which conflicts with the Redhat 7 package
postgresql-libs
What it intentional to start requiring the package libpq5 or could the
PyGreSQL package be set back to nly require the libpq.so.5()(64bit) which is
satisfied by the Redhat 7 package postgresql-libs?
I'm not sure, but there's also features which require recent client library, so
there's a balance between 1) not requiring brand new dependencies; and 2)
making new features available (without waiting for 5 years until their in the
then-oldest release).
This is one new feature:
| New query method memsize() that gets the memory size allocated by the query
(needs PostgreSQL >= 12 on the client).
--
Justin
_______________________________________________
_______________________________________________
PyGreSQL mailing list
PyGreSQL@Vex.Net
https://mail.vex.net/mailman/listinfo/pygresql
