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 1ssSYP-008ZOi-9o for pgsql-general@arkaria.postgresql.org; Sun, 22 Sep 2024 19:47:33 +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 1ssSYO-00BO2F-0T for pgsql-general@arkaria.postgresql.org; Sun, 22 Sep 2024 19:47:32 +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 1ssSYN-00BO26-Ly for pgsql-general@lists.postgresql.org; Sun, 22 Sep 2024 19:47:31 +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 1ssSYJ-000Woq-A7 for pgsql-general@lists.postgresql.org; Sun, 22 Sep 2024 19:47:30 +0000 Received: by rorschach.hjp.at (Postfix, from userid 1000) id 273A61B2A; Sun, 22 Sep 2024 21:47:25 +0200 (CEST) Date: Sun, 22 Sep 2024 21:47:25 +0200 From: "Peter J. Holzer" To: pgsql-general@lists.postgresql.org Subject: Re: glibc updarte 2.31 to 2.38 Message-ID: <20240922194725.aaa5hirtbkwwx6m6@hjp.at> Mail-Followup-To: pgsql-general@lists.postgresql.org References: <20240919174349.grrz4w25jmxfk77a@hjp.at> <58CD40AA-6316-40B6-89C2-390D16FF5FA0@gmail.com> <20240920223316.muvdgqekzh6dvcii@hjp.at> <2D395465-69B2-46C9-9B6A-84BF73D2379A@gmail.com> <5b0f58e4-f0cd-4a27-91bd-9a83a65c86d5@aklaver.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="mr2w5jrrruigbs24" Content-Disposition: inline In-Reply-To: <5b0f58e4-f0cd-4a27-91bd-9a83a65c86d5@aklaver.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --mr2w5jrrruigbs24 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2024-09-22 09:53:58 -0700, Adrian Klaver wrote: > On 9/22/24 09:48, Paul F=F6rster wrote: > > Then I strongly suggest that the PostgreSQL developers develop a > > fail safe sorting mechanism that holds for generations of locale > > changes. >=20 > https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-HIGHLIGHTS >=20 > Add a builtin platform-independent collation provider (Jeff Davis) >=20 > This supports C and C.UTF-8 collations. Couldn't you always use "C" collation? The problem with that is that most people[1] want stuff ordered according to the rules of their language and C collation is in most cases very different. hp [1] I actually have LC_COLLATE=3DPOSIX set in the shell. But I'm not normal. --=20 _ | Peter J. Holzer | Story must make more sense than reality. |_|_) | | | | | hjp@hjp.at | -- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" --mr2w5jrrruigbs24 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEETtJbRjyPwVTYGJ5k8g5IURL+KF0FAmbwdEYACgkQ8g5IURL+ KF1KhA/5AZ4D1TV+x/4l3OlBqn54A1Oq826B319/uKof8qygz1tlNAGWlNNkPIk0 /U7cvd/9HFzE7SXtY0eWulcH/qMd2239SQUNAg0Cc35oIVO74c/LV+fvn/ZggdVF /Hnw6cKnNABf54giIfdpxsa9h6TQiVMEtpUiGdOtsUf1pU0z/+7jxXiToLihy4I0 LOB4GWPF2MJB/AIVNmuqEr5+99ZRGsYYkPNp+MGISF18AWeTDeb4K0mq94dd21tF sFMiPVVmfH1p19kqKveLYco42TeTMcGv8l9Zt68NmjRr1C2NHkWafhj/e0F1ZAyj VScyXjPuW5mZ4Hp44/6JfV3IjrlBz0IvCFpNx0CwYbMoNTKSyiyNE8fjHtWwdF/4 jYSLPtI39IEswlmwoZpFeBDAuQtZjcOmdWK+tkgeuquM2R56vf58h5LlEXoThU2y 9cpmLLCt48Jm/smjjN7j43d+hVr1fdT3naa6H4Nyz0E5Xi8NXtrMKiLfmfEpfPJ2 J7S4WS1pDCFQYAWq3tHH8P4EDKKPFFepqh7C38Hk0c9buJDI7Q8YlNkBVdj9VL+P EwrhBpLxbje828gAdLN8Y9ZgpGWx3CrwMewzY4w8LkvixYLvBEf36yqpqOwMZc+6 ov9ze+Be/OGRZTMMsiquJeHT3UEGaFf2K1I+9l2Ubp36YB7JDXY= =uakm -----END PGP SIGNATURE----- --mr2w5jrrruigbs24--