Revision as of 09:30, 27 September 2022

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

Update of PostgreSQL (postgresql and libpq components) in Fedora from version 14 to version 15 in the non-modular (main) builds.

PostgreSQL 15.0 Release Notes

Owner

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

Current status

Targeted release: Fedora Linux 37
Last updated: 2022-09-27
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

Update of PostgreSQL (postgresql and libpq components) in Fedora from version 14 to version 15 in the non-modular (main) builds.

This also involves moving the postgresql-static subpackage to libpq creating the libpq-static subpackage.

Plan

Prepare PostgreSQL 15 in Copr (TBD)
Rebuild important dependencies in Copr (TBD)
Debug and fix compatibility issues found in dependencies (a reasonable amount of non-critical in FTBFS state might be tolerable)
Prepare Pull requests in Rawhide
Merge and build PR into Rawhide

Feedback

Benefit to Fedora

The latest stable software is used by Fedora users, providing additional features and fixes.

Scope

Proposal owners:
- Prepare PostgreSQL 15
- Prepare PostgreSQL 14 as a module for Rawhide
- Check software that requires or depends on postgresql-server or libpq packages for incompatibilities
- Build PostgreSQL 15 (postgresql and libpq) to Rawhide
- Rebuild depended on packages against PostgreSQL 15
- Gather user input on the changes between PostgreSQL 14 and PostgreSQL 15

Other developers: N/A (not a System Wide Change)

Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)

Policies and guidelines: N/A (not a System Wide Change)

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

Upgrade/compatibility impact

The PostgreSQL client library (libpq component) is compatible. So, there shouldn't be any compatibility issues, but rebuilding the dependent components is recommended.

Server plugins might require a newer version update because they sometimes have explicit server requirements. PostgreSQL maintainer will help fix/rebuild any issues in the plugins.

How to upgrade your database data from one PostgreSQL release to a newer one is described in Upgrading a PostgreSQL Cluster

How To Test

Usual testing when upgrading between major PostgreSQL versions is running postgresql-setup --upgrade necessary between major versions.

Test that all other software runs well with PostgreSQL 15.

User Experience

The users will have to upgrade their databases the same way as major PostgreSQL versions, aka postgresql-setup --upgrade after installing PostgreSQL 15 server packages.

If users want to stick with PostgreSQL 14 for a little longer, there will be PostgreSQL 14 module.

Dependencies

Some packages (mostly server plugins) build on top of PostgreSQL. Since the separation of the 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 make sure all potential binary incompatibilities are handled.

PostgreSQL server dependencies
- 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

Revert changes in the non-modular packages and provide PostgreSQL 15 as a module stream only.

Documentation

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

Release Notes

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

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

@@ Line 99: / Line 99: @@
 <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+Remember that you are writing this how-to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
 A good "how to test" should answer these four questions:
@@ Line 106: / Line 106: @@
 . How do I prepare my system to test this change? What packages
 need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
+. What specific actions do I perform to ensure the change works as it should?
-working like it's supposed to?
 . What are the expected results of those actions?
 -->
-Usual testing as when upgrading between major PostgreSQL versions, running postgresql-setup --upgrade is necessary between major versions.
+Usual testing when upgrading between major PostgreSQL versions is running `postgresql-setup --upgrade` necessary between major versions.
 Test that all other software runs well with PostgreSQL 15.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+<!-- REQUIRED FOR SYSTEM-WIDE CHANGES -->
 == User Experience ==

Search

Changes/PostgreSQL 15: Difference between revisions