Latest revision as of 20:40, 28 February 2024

PostgreSQL 16

Summary

Update of default PostgreSQL stream (postgresql and libpq components) in Fedora from version 15 to version 16. Since modularity was marked as retired, there will also be a change in the packaging concept.

Owner

Name: Filip Januš
Email: fjanus@redhat.com

Current status

Targeted release: Fedora Linux 40
Last updated: 2024-02-28
Announced
Discussion thread
FESCo issue: #3100
Tracker bug: #2251109
Release notes tracker: #1098

Detailed Description

The original package PostgreSQL will be retired. Since Fedora 40 there will be a separate component in the rpms namespace for each shipped PostgreSQL. So postgresql15 for PG15 and postgresql16 for PG16. Each PG stream will provide postgresql symbol and conflict with each other. The choice of default stream will be made by building sub-packages with appropriate names. (using -n in the files section). This approach should solve, among other things, the problem of possible duplicity. There is the following problem if we kept one version to be shipped in unversioned postgresql component:

F40 - there is currently a default version PG15 (postgresql -> 15)
F40 - there will be added version PG16 (postgresql -> 15, postgresql16)
F40 - switch default version to PG16 (postgresql -> 16, postgresql16, new postgresql15)
If PG15 is to be present in F40, to follow non-modular concept the new package is necessary.
BUt such switch leads to duplicit packages postgresql and postgresql16 with the same content.

Using just versioning packages would solve the described issue. The proposed solution is described below.

Plan of the future structure of Postgresql versioning:
Fedora 40 where PostgreSQL 16 is default:
postgresql SRPM -> deprecated
postrgresql15 SRPM -> postgresql15, postgresql15-server, ...
postrgresql16 SRPM -> postgresql, postgresql-server, ...
postrgresql17 SRPM -> postgresql17, postgresql17-server, ...

Fedora 42 where PostgreSQL 17 is default:
postgresql SRPM -> deprecated
postrgresql15 SRPM -> postgresql15, postgresql15-server, ...
postrgresql16 SRPM -> postgresql16, postgresql16-server, ...
postrgresql17 SRPM -> postgresql, postgresql-server, ...

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. Modules are no longer needed.

Scope

Proposal owners:

- Prepare PostgreSQL 16 as the default stream
- Prepare PostgreSQL 15 as a non-default stream
- Check software that requires or depends on postgresql-server or libpq packages for incompatibilities
- Build PostgreSQL 16 (postgresql and libpq) for Rawhide
- Build PostgreSQL 15 for Rawhide
- Rebuild dependent packages against PostgreSQL 16

Other developers:

Release engineering: #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Community Initiatives:

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 16.

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 16 server packages.

If users want to stick with PostgreSQL 15 for a little longer, there will be PostgreSQL 15 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: (What to do? Who will do it?) 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), Yes/No

Revert the changes and provide PostgreSQL 15 only.

Documentation

Upgrade strategy: https://www.postgresql.org/docs/16/upgrading.html

N/A (not a System Wide Change)

Release Notes

Release notes for PostgreSQL 16 release: https://www.postgresql.org/docs/16/index.html

Overall overview of the changes and improvements: https://www.postgresql.org/docs/16/release-16.html

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+= PostgreSQL 16 =
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= PostgreSQL 16 <!-- The name of your change proposal --> =
-{{Change_Proposal_Banner}}
 == Summary ==
-Update of default PostgreSQL stream (`postgresql` and `libpq` components) in Fedora from version 15 to version 16. Since no more modules are supported, there will also be a change in the packaging concept.
+Update of default PostgreSQL stream (`postgresql` and `libpq` components) in Fedora from version 15 to version 16. Since modularity was marked as retired, there will also be a change in the packaging concept.
 == Owner ==
@@ Line 25: / Line 16: @@
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 -->
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF40]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 46: / Line 38: @@
 ON_QA -> change is fully code complete
 -->
-* [<will be assigned by the Wrangler> devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/ZGUIEYJRB6TRBBDNPX6CUIT4SNKWXT6T/ Announced]
-* FESCo issue: <will be assigned by the Wrangler>
+* [https://discussion.fedoraproject.org/t/f40-change-proposal-postgresql-16-self-contained/92811 Discussion thread]
-* Tracker bug: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/3100 #3100]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2251109 #2251109]
+* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/1098 #1098]
 == Detailed Description ==
-The original package `PostgreSQL` will be retired. From Fedora 40 there will be a separate component in the rpms namespace for each shipped PostgreSQL. So postgresql15 for PG15 and postgresql16 for PG16. Each PG stream will provide `postgresql` symbol and conflict with each other. The choice of default stream will be made in
+The original package `PostgreSQL` will be retired. Since Fedora 40 there will be a separate component in the rpms namespace for each shipped PostgreSQL. So postgresql15 for PG15 and postgresql16 for PG16. Each PG stream will provide `postgresql` symbol and conflict with each other. The choice of default stream will be made by building sub-packages with appropriate names. (using `-n` in the `files` section). This approach should solve, among other things, the problem of possible duplicity. There is the following problem if we kept one version to be shipped in unversioned postgresql component:
+F40 - there is currently a default version PG15 (postgresql -> 15)<br>
+F40 - there will be added version PG16 (postgresql -> 15, postgresql16)<br>
+F40 - switch default version to PG16 (postgresql -> 16, postgresql16, new postgresql15)<br>
+If PG15 is to be present in F40, to follow non-modular concept the new package is necessary. <br>
+BUt such switch leads to duplicit packages postgresql and postgresql16 with the same content. <br>
+Using just versioning packages would solve the described issue. The proposed solution is described below.
+Plan of the future structure of Postgresql versioning:<br>
+Fedora 40 where PostgreSQL 16 is default:<br>
+postgresql SRPM -> deprecated<br>
+postrgresql15 SRPM -> postgresql15, postgresql15-server, ...<br>
+postrgresql16 SRPM -> postgresql, postgresql-server, ...<br>
+postrgresql17 SRPM -> postgresql17, postgresql17-server, ...<br>
+Fedora 42 where PostgreSQL 17 is default:<br>
+postgresql SRPM -> deprecated<br>
+postrgresql15 SRPM -> postgresql15, postgresql15-server, ...<br>
+postrgresql16 SRPM -> postgresql16, postgresql16-server, ...<br>
+postrgresql17 SRPM -> postgresql, postgresql-server, ...<br>
+This also involves updating and rebuilding the PostgreSQL plugins that depend on postgresql server.
 == Feedback ==
@@ Line 59: / Line 78: @@
 == Benefit to Fedora ==
 <!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
-     Consider these Change pages from previous editions as inspiration:
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+The latest stable software is provided for Fedora users.
+Modules are no longer needed.
 == 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 16 as the default stream
+**Prepare PostgreSQL 15 as a non-default stream
+**Check software that requires or depends on `postgresql-server` or `libpq` packages for incompatibilities
+**Build PostgreSQL 16 (postgresql and libpq) for Rawhide
+**Build PostgreSQL 15 for Rawhide
+**Rebuild dependent packages against PostgreSQL 16
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 110: / Line 115: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+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.
@@ Line 128: / Line 136: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+All PG server plugins should be installable.
+`postgresql-setup --upgrade` command should succeed.
+Test that all other software runs well with PostgreSQL 16.
 == User Experience ==
@@ Line 141: / Line 152: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+The users will have to upgrade their databases the same way as between major PostgreSQL versions, aka `postgresql-setup --upgrade` after installing PostgreSQL 16 server packages.
+If users want to stick with PostgreSQL 15 for a little longer, there will be PostgreSQL 15 as nondefault PostgreSQL stream
 == Dependencies ==
@@ Line 147: / Line 163: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+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 ==
@@ Line 156: / Line 199: @@
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+Revert the changes and provide PostgreSQL 15 only.
 == Documentation ==
 <!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+Upgrade strategy: https://www.postgresql.org/docs/16/upgrading.html
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 170: / Line 215: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
+Release notes for PostgreSQL 16 release: https://www.postgresql.org/docs/16/index.html
+Overall overview of the changes and improvements: https://www.postgresql.org/docs/16/release-16.html

Search

Changes/PostgreSQL 16: Difference between revisions