Re: F38 proposal: PostgreSQL 15 (Self-Contained Change proposal)
On Wed, Oct 12, 2022 at 02:59:20PM -0400, Frank Ch. Eigler wrote: > Ben Cotton writes: > > > https://fedoraproject.org/wiki/Changes/PostgreSQL_15 > >[...] > > === 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 > > Does this rebase include automated migration of existing databases? If > not, are users expected to do it manually, based on upstream postgresql > docs? Need of manual migration always has been there, hasn't it? -- Tomasz TorczOnly gods can safely risk perfection, to...@pipebreaker.pl it's a dangerous thing for a man. — Alia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F38 proposal: PostgreSQL 15 (Self-Contained Change proposal)
Ben Cotton writes: > https://fedoraproject.org/wiki/Changes/PostgreSQL_15 >[...] > === 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 Does this rebase include automated migration of existing databases? If not, are users expected to do it manually, based on upstream postgresql docs? - FChE ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: PostgreSQL 15 (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/PostgreSQL_15 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. == Owner == * Name: [[User:osloup| Ondřej Sloup]] * Email: osl...@redhat.com == 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 * Release engineering: * 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 [https://www.postgresql.org/docs/15/upgrading.html 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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F38 proposal: PostgreSQL 15 (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/PostgreSQL_15 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. == Owner == * Name: [[User:osloup| Ondřej Sloup]] * Email: osl...@redhat.com == 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 * Release engineering: * 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 [https://www.postgresql.org/docs/15/upgrading.html 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 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
