Bug 16875 - postgresql 11 and 12 packages conflict, complicating upgrade/migration process
Summary: postgresql 11 and 12 packages conflict, complicating upgrade/migration process
Status: REOPENED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Christiaan Welvaart
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-01 20:27 CEST by David Walser
Modified: 2020-02-24 21:23 CET (History)
4 users (show)

See Also:
Source RPM: postgresql11, postgresql12
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2015-10-01 20:27:33 CEST 
One of my co-workers informed me of this conflict, which we should fix, because:
"This makes it harder than it needs to be to upgrade a database, because
you can't use pg_upgrade (which requires both sets of binaries to be
installed.)"

This was also mentioned on the dev mailing list:
http://article.gmane.org/gmane.linux.mageia.devel/48180  (ml.mageia.org is down)

Reproducible: 

Steps to Reproduce:
David Walser 2015-10-01 20:27:42 CEST

CC: (none) => fundawang

Comment 1 Christiaan Welvaart 2015-10-01 20:47:06 CEST 
Fedora solved this in a not-terribly-nice way by including the previous postgresql version with the pg_upgrade script (or something to that effect). Making all (future) postgresql major versions parallel installable might mean two database server try to start up (because enabling services by default is our policy AFAIK). The systemd service names would all need to be different, so one would not run:
  systemctl start postgresql
but instead:
  systemctl start postgresql9.4
Comment 2 David Walser 2015-10-01 21:16:12 CEST 
In the case of postgresql, I think it would make sense to not enable the service by default.  I also think if we're going to continue to package multiple versions, it would make sense to make their service names not conflict, as you demonstrated.
Comment 3 David Walser 2016-02-27 22:25:08 CET 
Here's the correct mailing list link:
https://ml.mageia.org/l/arc/dev/2015-09/msg00656.html

It would be nice if we could solve this for postgresql9.4 and postgresql9.5 before Mageia 6.

CC: (none) => oe

Comment 4 Marja Van Waes 2017-03-29 07:27:36 CEST 
(In reply to David Walser from comment #3)
> Here's the correct mailing list link:
> https://ml.mageia.org/l/arc/dev/2015-09/msg00656.html
> 
> It would be nice if we could solve this for postgresql9.4 and postgresql9.5
> before Mageia 6.

So, did that happen or should this report be set to Cauldron and Mageia5TOO? If the latter, should it be a release blocker?

CC: (none) => marja11

Comment 5 Marja Van Waes 2017-03-29 07:28:00 CEST 
s/Mageia5TOO/MGA5TOO/
Comment 6 David Walser 2017-03-29 11:52:49 CEST 
Indeed this hasn't been addressed.  It could be fixed post-release (though obviously it would be ideal to fix it before) so it doesn't need to be a blocker.  It's not worth fixing for Mageia 5 at this point.

Version: 5 => Cauldron
Source RPM: postgresql9.3, postgresql9.4 => postgresql9.4, postgresql9.6
Summary: postgresql 9.3 and 9.4 packages conflict, complicating upgrade/migration process => postgresql 9.4 and 9.6 packages conflict, complicating upgrade/migration process

Comment 7 Marc Krämer 2020-02-24 20:46:16 CET 
this issue is fixed and old.

CC: (none) => mageia
Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 8 David Walser 2020-02-24 21:23:17 CET 
No it hasn't been fixed.

Resolution: OLD => (none)
Status: RESOLVED => REOPENED
Summary: postgresql 9.4 and 9.6 packages conflict, complicating upgrade/migration process => postgresql 11 and 12 packages conflict, complicating upgrade/migration process
Source RPM: postgresql9.4, postgresql9.6 => postgresql11, postgresql12
Note You need to log in before you can comment on or make changes to this bug.