Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1skROJ-0008ZJ-63 for pgsql-general@arkaria.postgresql.org; Sat, 31 Aug 2024 16:55:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1skRNJ-000VDG-6M for pgsql-general@arkaria.postgresql.org; Sat, 31 Aug 2024 16:54:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1skRNI-000V22-Qq for pgsql-general@lists.postgresql.org; Sat, 31 Aug 2024 16:54:57 +0000 Received: from mail.hjp.at ([212.17.106.138] helo=rorschach.hjp.at) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1skRNA-0000Si-Op for pgsql-general@postgresql.org; Sat, 31 Aug 2024 16:54:54 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id 9648B9613; Sat, 31 Aug 2024 18:54:45 +0200 (CEST) Date: Sat, 31 Aug 2024 18:54:45 +0200 From: "Peter J. Holzer" To: pgsql-general@postgresql.org Subject: Upgrade Ubuntu 22 -> 24 may break PostgreSQL Message-ID: <20240831165445.7kqb4ezzghaysbc7@hjp.at> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3fib4y5dmzajgywj" Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --3fib4y5dmzajgywj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 'Tis the season again. Ubuntu 24.04.1 has just been released, so many Ubuntu LTS users will now be prompted to upgrade from 22.04 to 24.04. A word of warning to those who use Postgresql from the Ubuntu repo (not PGDG): As usual, a newer Ubuntu version comes with a newer Postgres version (16 instead of 14). Also as usual, I got a message during the upgrade that Postgres 14 is obsolete,. but the binaries have been left installed and I should upgrade to Postgres 16 manually ASAP. But after the reboot, PostgreSQL failed to start because it needed a shared library (libldap) which was no longer there. So a normal pg_upgradecluster wouldn't work. In my case the quickest way to recover was to install postgresql-14 on a VM, copy the data direcory into that instance and make a fresh dump, then install postgresql-16 on my laptop and restore the dump. Annoying, but no big deal for the small test database I keep on my laptop. If you have multi-terabyte databases, your situation may be different. I'm not exactly sure what went wrong (I got some conflicts during the upgrade and maybe I shouldn't have invoked apt autoremove?), and you may not have this problem, but make sure you have a backup before the upgrade. hp --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --3fib4y5dmzajgywj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmbTSs8ACgkQ8g5IURL+ KF3fyw/+JcA9n3Bu/N63+2DjX0nZUZ1Jt/lgu9ztziouI6E1fBE/0maLG2si7P9S H8lQjnb+EOJ2PM2uX5mpe7seH3XBrrxk7qmohVKaDAHsvm8dD/Tq3gzeFrJBMFbl PydPAN0ys+9FJ25DaeA4GH0oJEpSkahzRRQriUFd+Mm0EqzmAhk98qh0EtK38Y7c 2tmiJZLf//bU001JPllrI3qFuKXeUAaNCUy2PuLoM1SjKMXDWqY69djQPh9gpxbB Uzkg+S9v9luToytpxm8hdm+5Qc8S+Vr2reK5xE9YYLgZUsx62DAT43b2wlJZvezh Afcjrffd8fJ33fSjhB1Pus40So7ZhBg1s4N2W1NxAo1iFflmi0vm0aMUZrmVA6l+ 8BGX6jQJkJL1qGlm0RiBmm/LAvWH7bORnBuYmCCMFzBxKzBA4PLRUCjfDQo68rc/ 2Tw+zoSF6MwtLLOYHZCGPMC1IZJVl468e8gORfJn9Kk5YTv1nIG8fdO5ooMACIT9 kJ6ICwpD54mnPdvkUgBQ9j7C1IIDA2tBDF5p9leJOXdhaqaByZj15szlSnwPpQKS TWe1i+BsDrdrO2XSZ9bHLwYxTRLY3urDJhAXrIBSS0Vs3UZO5YRHwQc1lb62+cVG kFTBPwscvR1UafkuXxqgol2WZQffkL2Gs7KdlVPxy9ToNAzVqzo= =BGVx -----END PGP SIGNATURE----- --3fib4y5dmzajgywj--