From Fedora Project Wiki
(Created page with "= PostgreSQL 13 <!-- The name of your change proposal --> = == Summary == Update of PostgreSQL (`postgresql` and `libpq` components) in Fedora from version 12 to version 13 i...")
 
(Announcing the change proposal)
Line 21: Line 21:


== Current status ==
== Current status ==
[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAnnounced]]
<!-- 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 -->

Revision as of 19:15, 7 July 2020

PostgreSQL 13

Summary

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

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-07-07
  • 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 12 to version 13 in the non-modular (main) builds.

This also involves updating and rebuilding the PostgreSQL plugins that depend on postgresql server.

Feedback

Benefit to Fedora

Latest stable software is used by Fedora users.

Scope

  • Proposal owners:
    • Prepare PostgreSQL 13 as a module for Rawhide and at least one stable Fedora release (done)
    • Prepare PostgreSQL 12 as a module for Rawhide, so there would be a failover in case of problems
    • Build PostgreSQL 13 to Rawhide
    • Check software that requires or depends on postgresql-server or libpq packages for incompatibilities
    • Gather user input on the changes between PostgreSQL 12 and PostgreSQL 13
  • 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 issues, but rebuild of the depended components is better to be sure. There is a COPR build available for testing. Server plugins might require a newer version update, because they sometimes have explicit server requirements. PostgreSQL maintainer will help fixing/rebuilding any issues in the plugins.

How To Test

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

Test that all other software runs well with PostgreSQL 13.

User Experience

The users will have to upgrade their databases the same way as between major PostgreSQL versions, aka postgresql-setup --upgrade.

If users want to stick with PostgreSQL 12 for a little longer, there should be PostgreSQL 12 module. If users want to test it before it reaches Fedora 33, there is a COPR build available.

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 both the cases, rebuild should be done to make sure all potential binary incompatibilities are handled.

Contingency Plan

Modules will provide the functional version of PostgreSQL 12, available to all users.

Documentation

Upgrade startegy: https://www.postgresql.org/docs/13/upgrading.html

Release Notes

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

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