This issue is intended as a space for discussing the possible changes to Postgresql in Fedora. We propose multiple changes, but the main one is demodularization. There are many issues with maintaining modules across components. So we would like to propose a new concept for shipping multiple versions of PostgreSQL. Python chose a similar approach. Proposed changes: - Demodularization - Proposed approach https://src.fedoraproject.org/rpms/postgresql/pull-request/59 - Stop shipping pdf documentation - Support upgrades from various versions using the upgrade subpackage. Currently is possible to upgrade only from the previous major version. - It should not be necessary to maintain extensions for each PostgreSQL version. - Currently, we have in each module a separate instance of extensions(pgaudit,pg_repack,...) Please share your thoughts and ideas.
(In reply to Filip Januš from comment #0) > - Demodularization No opinion on this. > - Stop shipping pdf documentation +1 > - Support upgrades from various versions using the upgrade subpackage. +1 > - It should not be necessary to maintain extensions for each PostgreSQL > version. You'll find this is only possible for extensions that have no server-side loadable library, which is hardly any of them. Internally to the server, upstream only tries to maintain ABI compatibility within a major version series, and there are actually mechanisms to reject a library that was built for another major version. So I doubt this goal is achievable.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
*** Bug 2147566 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
I think if you use the futurefeaure keyword, this bug will stay attached to rawhide.
I'd like to eventually see parallel installs be available. I run Postgres on my laptops and desktops with various (small) data sets and I'd like to be able to try out the next major release without needing to immediately switch everything over to keep stuff working. I could switch to the Postgres upstream builds (I use them for RHEL servers at work), but prefer to run Fedora builds on Fedora.
Whatever was causing the build problem seems to have been external to stratagus. It built successfully without changing anything in the package.
Sorry, I was looking at two bugs and got mixed up when trying to close the stratagus one.
Thank you for your reply. but parallel installation is not considered nowadays. To solve your problem, I can recommend to use containers. This changes where implemented so I am closing this issue.