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 1srLCB-000jsh-Gl for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 17:44:00 +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 1srLC9-005Ap0-EN for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 17:43:58 +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 1srLC9-005Aor-3h for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 17:43:58 +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 1srLC4-0002iQ-Es for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 17:43:57 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id 40C1E1237E; Thu, 19 Sep 2024 19:43:49 +0200 (CEST) Date: Thu, 19 Sep 2024 19:43:49 +0200 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: glibc updarte 2.31 to 2.38 Message-ID: <20240919174349.grrz4w25jmxfk77a@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zpjw4crql7qbdnyd" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --zpjw4crql7qbdnyd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2024-09-19 16:37:41 +0200, Paul Foerster wrote: > we have SLES 15.5 which has glibc 2.31. Our admin told us that he's > about to install the SLES 15.6 update which contains glibc 2.38. >=20 > I have built our PostgreSQL software from source on SLES 15.5, because > we have some special requirements which the packages cannot fulfill. > So I have questions: >=20 > 1) Do I have to build it again on 15.6? >=20 > 2) Does the glibc update have any impact? I recall having to have > everything reindexed when the 2.28 update came due to major locale > changes, but I didn't have to do it since then. >=20 > 3) Where and how can I find out if it is necessary to reindex? I wrote a small script[1] which prints all unicode code points and a few selected[2] longer strings in order. If you run that before and after the upgrade and the output doesn't change, you are probably be fine. (It checks only the default collation, though: If you have indexes using a different collation you would have to modify the script accordingly.) If there are differences, closer inspection might show that the changes don't affect you. But I would reindex all indexes on text (etc.) columns just to be sure. hp [1] https://git.hjp.at:3000/hjp/pgcollate [2] The selection is highly subjective and totally unscientific. Additions are welcome. --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --zpjw4crql7qbdnyd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmbsYs8ACgkQ8g5IURL+ KF05IQ/9FpSEI3sEcODFxoJTPJztxYYdghi1m/j0K9tpZE3Nv8z4dhPMAyLr0x81 P5q0COC7tboGQV+mOvau7cTP1zNvDZHwK7UlGzKBNBbQcgOMpXi56vr3t56f3FD+ Vgb9b74a3Y+H3pRhoHrGjuAj7GUn/YCJKe+ilYCVYzbDTbgSQX38VLQi9wTbSRiV FzWKfsKjgZ7w7GC8fnETtufmNlKG8XS++Dqu8IwNk4aDwxJ999HfGse4Vc71+KzG NSEcbgCv4T+r7pI5zrcEt4nxOw+So9+WIlEAohTb0sQnGwSzkn8EB+qqylyog9RU 2b0f7DkiBYVGaEOBxhMT2xz7iTKPVLnHKWGFbC7eshc3kFpLJL94eScQ28ZudrS1 BgSNBaDHoPxvYsx1Z8GOPNheCmDlkjI/l5M/i5mPPRzQ58SSH0Vzf/1yBWwAHYk/ GqvbudyreBIrZERoumnbj2ECoOIeTT0tVndTabmntvl7HWcCVjkaJH9e23gGqV4r aI8Xc/QaTrF2xfVjd0LBnTtPF71gAEQhREVTX5BfwySmVjfC6TueFuGV6SGcKJeq eneGc1x467BQ/4cD5M54W+8EyGRfNLES6u0NcWSbqCcHE7a4Y+fK+XJZgQ19MVjC GZ/D3TYPutHX3Po+KyuCAs1YKTfLJ0WwbK4XGmORR7ZnA/ivlOw= =23sF -----END PGP SIGNATURE----- --zpjw4crql7qbdnyd--