From Fedora Project Wiki
No edit summary
 
(40 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Change Proposal Name PostgreSQL 15 =
= PostgreSQL 15 =


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


== Summary ==
[https://www.postgresql.org/docs/release/15.0/ PostgreSQL 15.0 Release Notes]
<!-- 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 Fedora section below, and this part should answer the question "What?" rather than "Why?". -->


== Owner ==
== Owner ==
Line 11: 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:FASAcountName| Your Name]]
* 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: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
* 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>
-->
-->
 
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
* Product:
* 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 30: Line 33:
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/<number> | Fedora Linux <number> ]]  
* 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 38: 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 ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
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 ==
== Feedback ==
Line 49: Line 65:


== Benefit to Fedora ==
== 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?
The latest stable software is used by Fedora users, providing additional features and fixes.
 
      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)
-->


== Scope ==
== Scope ==
* Proposal owners:
* 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?-->
<!-- 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 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: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers 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?-->
<!-- What work do other developers 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?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->


* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
 
* Alignment with Objectives:
<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
The PostgreSQL client library (libpq component) is compatible. So, there shouldn't be any compatibility issues, but rebuilding the dependent components is recommended.


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
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
[https://www.postgresql.org/docs/15/upgrading.html Upgrading a PostgreSQL Cluster]


== How To Test ==
== How To Test ==
<!-- 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.  
<!-- 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:
A good "how to test" should answer these four questions:
Line 113: Line 108:
1. How do I prepare my system to test this change? What packages
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
2. What specific actions do I perform to ensure the change works as it should?
working like it's supposed to?
3. What are the expected results of those actions?
3. What are the expected results of those actions?
-->
-->
Usual testing when upgrading between major PostgreSQL versions is running `postgresql-setup --upgrade` necessary between major versions.


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Test that all other software runs well with PostgreSQL 15.
 
<!-- REQUIRED FOR SYSTEM-WIDE CHANGES -->


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
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.


This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
If users want to stick with PostgreSQL 14 for a little longer, there will be PostgreSQL 14 module.


Describe what Users will see or notice, for example:
== Dependencies ==
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== 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.
<!-- 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)? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* 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 ==
== Contingency Plan ==
 
Revert changes in the non-modular packages and provide PostgreSQL 15 as a module stream only.
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
Upgrade strategy: https://www.postgresql.org/docs/15/upgrading.html
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
Release notes for PostgreSQL 15 release: https://www.postgresql.org/docs/15/index.html
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.  


Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
Overall overview of the changes and improvements: https://www.postgresql.org/docs/15/release-15.html
-->

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"