Wiki - https://fedoraproject.org/wiki/Changes/PostgreSQL_18 Discussion thread - https://discussion.fedoraproject.org/t/f43-change-proposal-postgresql-18-self-contained/158044/2
This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Update of default PostgreSQL stream (`postgresql` and `libpq` components) in Fedora from version 16 to version 18. This continues the versioned packaging structure introduced in Fedora 40. == Owner == * Name: [[User:ndavidov| Nikola Davidová]] * Email: ndavi...@redhat.com == Detailed Description == Following the Fedora 40+ PostgreSQL packaging model, each major version of PostgreSQL is delivered as a separate SRPM. The default PostgreSQL stream is selected by naming the packages as postgresql, postgresql-server, etc., while non-default versions use versioned names like postgresql17. For Fedora 43, the PostgreSQL 18 SRPM will provide the default PostgreSQL implementation. The following mapping will apply: postgresql SRPM -> deprecated postgresql16 SRPM -> postgresql16, postgresql16-server, ...<br> postgresql17 SRPM -> postgresql17, postgresql17-server, ...<br> postgresql18 SRPM -> postgresql, postgresql-server, ...<br> This also involves updating and rebuilding the PostgreSQL plugins that depend on postgresql server. == Feedback == == Benefit to Fedora == The latest stable software is provided for Fedora users. == Scope == * Proposal owners: <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> **Prepare PostgreSQL 18 as the default stream **Prepare PostgreSQL 16 as a non-default stream **Check software that requires or depends on `postgresql-server` or `libpq` packages for incompatibilities **Build PostgreSQL 18 (postgresql and libpq) for Rawhide **Build PostgreSQL 16 for Rawhide **Rebuild dependent packages against PostgreSQL 18 * Other developers: * Release engineering: [https://pagure.io/releng/issues #Releng issue number] * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Fedora Strategy: == Upgrade/compatibility impact == The PostgreSQL client library (libpq component) is compatible. So, there shouldn't be any compatibility issues, but rebuild of the dependent components is recommended. Server plugins might require a newer version update because they sometimes have explicit server requirements. == How To Test == All PG server plugins should be installable. `postgresql-setup --upgrade` command should succeed. Test that all other software runs well with PostgreSQL 18. == User Experience == The users will have to upgrade their databases the same way as between major PostgreSQL versions, aka `postgresql-setup --upgrade` after installing PostgreSQL 18 server packages. If users want to stick with PostgreSQL 16 for a little longer, there will be PostgreSQL 16 as nondefault PostgreSQL stream == Dependencies == There are some packages (mostly server plugins), that build on top of PostgreSQL. Since the separation of PostgreSQL client library (libpq component), only packages that build server plugins should use postgresql package in BuildRequires. Others should use libpq. In the case of Postgresql-server, a rebuild should be done to ensure all potential binary incompatibilities are handled. * PostgreSQL server dependecies ** perl-DBD-Pg ** pgaudit ** qt ** qt3 ** qt5-qtbase ** postgres-decoderbufs ** gambas3 ** kdb ** kea ** libpqxx ** openvas-manager ** orafce ** pg-semver ** pgRouting ** pgadmin3 ** pgsphere ** postgis ** postgresql-ip4r ** postgresql-pgpool-II ** qt3 ** rdkit ** rhdb-utils ** timescaledb ** pg_repack == Contingency Plan == * Contingency mechanism: N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) Revert the changes and provide PostgreSQL 16 only. == Documentation == Upgrade strategy: https://www.postgresql.org/docs/18/upgrading.html N/A (not a System Wide Change) == Release Notes == Release notes for PostgreSQL 18 release: https://www.postgresql.org/docs/18/index.html Overall overview of the changes and improvements: https://www.postgresql.org/docs/18/release-18.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
