Re: F42 Change Proposal: Retirement of PostgreSQL 15 (Self-Contained)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Can I ask why this hasn't gotten the FESCo issue yet?

On Tue, Nov 12, 2024 at 11:16 PM Aoife Moloney via devel-announce <devel-announce@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Wiki - https://fedoraproject.org/wiki/Changes/RemovalPostgreSQL15
Discussion Thread -
https://discussion.fedoraproject.org/t/f42-change-proposal-retirement-of-postgresql-15-self-contained/136636

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 [[Changes/PostgreSQL 16|PostgreSQL16 change]]),
and version 17 would be the alternative.

== Owner ==

* Name: [[User:ljavorsk| Lukas Javorsky]], [[User:fjanus| Filip Janus]]

* Email: ljavorsk@xxxxxxxxxx, fjanus@xxxxxxxxxx


== 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 ==
* Proposal owners:

** Follow the [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
Package Retirement Process]

* Other developers:

* Release engineering: [https://pagure.io/releng/issues #Releng issue number]

* 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
standard upgrade strategy should be followed:
# Dump and restore upgrade
## Stop the `postgresql` service
## Dump the databases using `su - postgres -c "pg_dumpall >
/PATH/TO/pgdump_file.sql"`
## Backup all of the data in `/var/lib/pgsql/data/`
## Enumerate all postgresql-based packages by `rpm -qa | grep postgresql`
## Upgrade all installed (enumerated in the previous step) PostgreSQL
packages using (e.g. for upgrading to PG-16) `dnf install
PACKAGE_NAMES --allowerasing`
## Copy the old configuration files to the `/var/lib/pgsql/data/`
## Start the `postgresql` service
## Import data from the dumped file using `su - postgres -c 'psql -f
/PATH/TO/pgdump_file.sql postgres'`
# Fast upgrade using the pg_upgrade utility
## Stop the `postgresql` service
## Backup all of the data in `/var/lib/pgsql/data/`
## Enumerate all postgresql-based packages by `rpm -qa | grep postgresql`
## Upgrade all installed (enumerated in the previous step) PostgreSQL
packages using (e.g. for upgrading to PG-16) `dnf install
PACKAGE_NAMES --allowerasing`
## Install the upgrade package `dnf install postgresql-upgrade`
## Run `postgresql-setup --upgrade`
## Copy the old configuration files to the `/var/lib/pgsql/data/`
## Run `# systemctl start postgresql.service`


== 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)


== Documentation ==

N/A (not a System Wide Change)

== Release Notes ==


--
Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney

--
_______________________________________________
devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue


--
S pozdravom/ Best regards

Lukáš Javorský

Senior Software Engineer, Core service - Databases

Red Hat

Purkyňova 115 (TPB-C)

612 00 Brno - Královo Pole

ljavorsk@xxxxxxxxxx

-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux