Public bug reported:
As reported against "#2078494 After upgrade to 24.04.1 LTS
pg_upgradecluster fails":
On my standby pc, I upgraded today from 22.04 to 24.04.1
After the upgrade /usr/lib/postgresql/14/bin/postgres and the named libraries
were all still in place.
pg_lsclusters showed the old (v.14) and the new (v.16) clusters, as expected.
So I dropped the new v.16 cluster with "--stop", and ran pg_upgradecluster 14
main.
That *appeared* to finish ok this time - except that it didn't.
The new v.16 cluster was left with the new port (5433), did not have me as an
admin user, and didn't have any of the databases that should have been upgraded.
I copied the screen output to pg_upgradecluster.OUT, which I will upload;
and I'm shutting down the standby pc in this strange condition, in case
questions need to be answered.
Not quite the same as on my main pc, but the error is probably related
none-the-less.
New bug report as per request of Athos Ribeiro <2078...@bugs.launchpad.net>.
I tried to report this from the standby pc, but the screen pointer disappeared
after I'd entered my login name to launchpad, and then that pc rebooted.
Perhaps the collected data is still in a file there somewhere? If so, then I
can recover it and attach to this report...
** Affects: postgresql-16 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081996
Title:
After upgrade to 24.04.1 LTS pg_upgradecluster fails to upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
