On Sun, Nov 30, 2025 at 05:35:26PM -0800, Emmett Culley via users wrote: > I waited to upgrade from Fedora 42 to 43 until today, while watching the > various fedora mailing lists for issue that could cause problems for my > multiple Fedora systems. After successfully updating four other systems I > decided it was safe to upgrade my personal workstation. > > After the final reboot I found that PostgreSql did not start. > > Turns out 43 skipped over version 17 and went to version 18. This prevented > the upgrade process from my PostgreSql 16 databases. > > I found a bug report report from 11/1 about this. First time I heard about > it as it never showed up on any of the lists I subscribe to. > > I followed the instructions in the bug report, but sure enough, as they > warned, they didn't work. > > Now what do I do?
This should explain the process: https://docs.fedoraproject.org/en-US/quick-docs/postgresql/#skipped-release basically, downgrade to 17, upgrade your 16 database to 17, then update to 18 and upgrade your db again. ;( kevin -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
