The community PostgreSQL YUM repository does not just include PostgreSQL packages, but also some extensions which depend on a specific PostgreSQL version (e.g. PostGIS.), packages in the PostgreSQL world which can be used against some (or all) PostgreSQL versions (e.g. pgAdmin4), and the supportive packages for those extensions (e.g. Proj, GeOS).
Until yesterday, all of these packages were contained inthe same directory for each OS / PostgreSQL combination. This increased both build time and the disk space required.
So, I decided to merge the “common” packages (packages like pgAdmin4 and GEOS as described above) into one single repository.
Yesterday I released new repo RPMs (42.0-9) which introduce 3 new common repositories:
I will add a pgdg-common-srpms repository later on.
If you are using the default repo file (without editing it), a yum/dnf update will automatically update the new repo configuration file. No additional action required. This applies to the majority of our user base.
If you have manually edited the repo file, installing the new repo RPM will not overwrite it . Instead, it will create a new file ending with .rpmnew. You will need to merge changes from that file to the .repo file.
Existing installations will continue running, and you will still receive “non-common” updates, in particular updates to the main PostgreSQL packages. However, new installations will fail when they need the common packages.
No. That will cause more issues.
Yes, as explained above.
I moved them to the common repository. Please update the repo file as described above.
Please send an email to email@example.com , or submit an issue in the community issue tracker: https://redmine.postgresql.org/projects/pgrpms/issuesPostgreSQL Project