Bug 2165557

Summary:	Future of packiging the Postgresql in Fedora
Product:	[Fedora] Fedora	Reporter:	Filip Januš <fjanus>
Component:	postgresql	Assignee:	Filip Januš <fjanus>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	39	CC:	anon.amish, bruno, devrim, fjanus, hhorak, jmlich83, mkulik, osloup, pkubat, praiskup, tgl
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-02-28 08:57:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Filip Januš 2023-01-30 12:33:03 UTC

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.

Comment 1 Tom Lane 2023-01-30 15:33:50 UTC

(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.

Comment 2 Ben Cotton 2023-02-07 15:07:14 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Filip Januš 2023-02-13 14:32:20 UTC

*** Bug 2147566 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Release Engineering 2023-08-16 07:06:33 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 5 Bruno Wolff III 2023-11-14 08:45:21 UTC

I think if you use the futurefeaure keyword, this bug will stay attached to rawhide.

Comment 6 Bruno Wolff III 2024-02-28 04:16:58 UTC

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.

Comment 7 Bruno Wolff III 2024-02-28 05:11:14 UTC

Whatever was causing the build problem seems to have been external to stratagus. It built successfully without changing anything in the package.

Comment 8 Bruno Wolff III 2024-02-28 05:13:03 UTC

Sorry, I was looking at two bugs and got mixed up when trying to close the stratagus one.

Comment 9 Filip Januš 2024-02-28 08:57:49 UTC

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.