From Fedora Project Wiki
(Created page with "<!-- 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 --> = Retirement of PostgreSQL 15 = {{Change_Proposal_Banner}} == Summary == <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedor...")
 
No edit summary
Line 49: Line 49:
== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
With the addition of PostgreSQL-17 to Fedora 42, maintaining multiple versions is no longer necessary and creates a significant capacity burden.
With the addition of PostgreSQL-17 to Fedora 42, maintaining PG15  is no longer necessary and creates a significant capacity burden.
This will also mean the retirement of the dependent components like `postgresql15-pgaudit`, `postgresql15-pg_repack`, and `postgresql15-decoderbufs`.
This will also mean the retirement of the dependent components like `postgresql15-pgaudit`, `postgresql15-pg_repack`, and `postgresql15-decoderbufs`.


Line 151: Line 151:
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->


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.
The following dependencies (stand-alone packages) will be retired alongside the postgresql15:
 
*`postgresql15-pgaudit`, `postgresql15-pg_repack`, and `postgresql15-decoderbufs`
* 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


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 07:59, 7 November 2024


Retirement of PostgreSQL 15

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

PostgreSQL version 15 will be retired from Fedora 42 since there are newer versions like 16 and 17. Version 16 is already the default version (announced in PostgreSQL16 change), and version 17 would be the alternative.

Owner


Current status

  • Targeted release: Fedora Linux 42
  • Last updated: 2024-11-07
  • [Announced]
  • [<will be assigned by the Wrangler> Discussion 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

With the addition of PostgreSQL-17 to Fedora 42, maintaining PG15 is no longer necessary and creates a significant capacity burden. This will also mean the retirement of the dependent components like postgresql15-pgaudit, postgresql15-pg_repack, and postgresql15-decoderbufs.

Feedback

Benefit to Fedora

Lesser PostgreSQL versions to maintain and newer versions with additional features.

Scope

  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy:

Upgrade/compatibility impact

In the case user's still didn't upgrade to the default stream 16, the upgrade strategy is described here: https://www.postgresql.org/docs/16/upgrading.html


Early Testing (Optional)

How To Test

The postgresql15* RPMs should not be in the Fedora mirrors and should not be installed.


User Experience

Dependencies

The following dependencies (stand-alone packages) will be retired alongside the postgresql15:

  • postgresql15-pgaudit, postgresql15-pg_repack, and postgresql15-decoderbufs


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), No


Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/RemovalPostgreSQL15&oldid=723986"