From Fedora Project Wiki
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= PostgreSQL 15 =
= PostgreSQL 15 =
{{Change_Proposal_Banner}}


== Summary ==
== Summary ==
Line 13: Line 11:
This should link to your home wiki page so we know who you are.  
This should link to your home wiki page so we know who you are.  
-->
-->
* Name: [[User:fjanus| Filip Januš]]
* Name: [[User:osloup| Ondřej Sloup]]
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: fjanus@redhat.com
* Email: osloup@redhat.com
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 23: Line 21:
* Responsible WG:
* Responsible WG:
-->
-->
== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF38]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 34: Line 33:
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/37 | Fedora Linux 37 ]]  
* Targeted release: [[Releases/38 | Fedora Linux 38 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 42: Line 41:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CJ5VDXJYMSMCTDP2RY672HPQF6NKT64G/ devel thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2882 #2882]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2139102 #2139102]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/894 #894]


== Detailed Description ==
== Detailed Description ==
Line 56: Line 56:
* Rebuild important dependencies 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)
* Debug and fix compatibility issues found in dependencies (a reasonable amount of non-critical in FTBFS state might be tolerable)
* Build in a "side tag" to prevent dependencies from failing and rollout once stable
* Prepare Pull requests in Rawhide
* Prepare Pull requests in Rawhide
* Merge and build PR into Rawhide
* Merge and build into a "side tag"
* Once stable merge into Rawhide


== Feedback ==
== Feedback ==
Line 115: Line 117:


== User Experience ==
== 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.
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.
If users want to stick with PostgreSQL 14 for a little longer, there will be PostgreSQL 14 module.
Line 129: Line 131:
** qt3
** qt3
** qt5-qtbase
** qt5-qtbase
** postgres-decoderbufs
** qt6-qtbase-postgresql
** postgres-decoderbufs – The package does not support PostgreSQL 15 yet. Hopefully, support will be added in the next release (Fixed in version 1.9.7)
** gambas3
** gambas3
** kdb
** kdb
** kea
** kea
** kexi
** libpqxx
** libpqxx
** openvas-manager
** orafce
** orafce
** pg-semver
** pg-semver
** pgRouting
** pg_auto_failover
** pgadmin3
** pgsphere
** pgsphere
** postgis
** postgis
** postgresql-ip4r
** postgresql-ip4r
** postgresql-pgpool-II
** postgresql-pgpool-II
** qt3
** rdkit
** rhdb-utils
** rhdb-utils
** timescaledb
** timescaledb – The package does not support PostgreSQL 15 yet. Hopefully, support will be added in the next release. Building with PostgreSQL 15 can be done with an experimental flag, but currently fails.
** pg_repack
** pg_repack
Copr with builder dependencies https://copr.fedorainfracloud.org/coprs/osloup/postgresql_update_15_2/


== Contingency Plan ==
== Contingency Plan ==

Latest revision as of 16:05, 2 December 2022

PostgreSQL 15

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

Current status

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)
  • Build in a "side tag" to prevent dependencies from failing and rollout once stable
  • Prepare Pull requests in Rawhide
  • Merge and build into a "side tag"
  • Once stable merge 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)
  • 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
    • qt6-qtbase-postgresql
    • postgres-decoderbufs – The package does not support PostgreSQL 15 yet. Hopefully, support will be added in the next release (Fixed in version 1.9.7)
    • gambas3
    • kdb
    • kea
    • kexi
    • libpqxx
    • orafce
    • pg-semver
    • pg_auto_failover
    • pgsphere
    • postgis
    • postgresql-ip4r
    • postgresql-pgpool-II
    • rhdb-utils
    • timescaledb – The package does not support PostgreSQL 15 yet. Hopefully, support will be added in the next release. Building with PostgreSQL 15 can be done with an experimental flag, but currently fails.
    • pg_repack

Copr with builder dependencies https://copr.fedorainfracloud.org/coprs/osloup/postgresql_update_15_2/

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

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