Revision as of 08:51, 2 October 2023

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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

PostgreSQL 16

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 15 to version 16. Since no more modules are supported, 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: 2023-10-02
[<will be assigned by the Wrangler> devel thread]
FESCo issue: <will be assigned by the Wrangler>
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

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 by building sub-packages with appropriate names. (using -n in the files section)

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 14

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

Dependencies

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

Documentation

N/A (not a System Wide Change)

Release Notes

@@ Line 52: / Line 52: @@
 == 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. 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 by building sub-packages with appropriate names. (using `-n` in the `files` section)
+This also involves updating and rebuilding the PostgreSQL plugins that depend on postgresql server.
 == Feedback ==
@@ Line 59: / Line 61: @@
 == 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 14
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 110: / Line 98: @@
 <!-- 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 119: @@
 <!-- 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 ==

Search

Changes/PostgreSQL 16: Difference between revisions