Date: Mon, 14 Apr 2025 19:18:46 +0200
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Thomas Michael Engelke
 <thomas.engelke@posteo.de>, pgsql-general@lists.postgresql.org
Subject: Re: ICU Collations and Collation Updates
Message-ID: <20250414191846.39b9415e@karst>
In-Reply-To: <1257278.1744641400@sss.pgh.pa.us>
References: <8ed41c50ba6c5322296b869e497c1b5573853b54.camel@posteo.de>
	<d477c1faf35bad99fe550c8c4c1954ffa076ccfd.camel@cybertec.at>
	<1257278.1744641400@sss.pgh.pa.us>
Organization: Dalibo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/20250414191846.39b9415e%40karst>
Precedence: bulk

Le Mon, 14 Apr 2025 10:36:40 -0400,
Tom Lane <tgl@sss.pgh.pa.us> a =C3=A9crit :
[=E2=80=A6]
> 2. It's at least *possible* to use your own fixed-version ICU
> library if you're desperate enough.  I don't think that would work
> too well for libc; you're stuck with what the platform provides.

You're not so stuck with what the plateform provides as you can define your=
 own
collation with glibc. Here a quick exemple with an ebcdic collation based on
glibc:

https://www.postgresql.org/message-id/flat/20230824162653.34eb3bad%40karst#=
31c548587bc98686e010e500a2f97d97

It's probably another level of maintenance to provide a stable UTF8 collati=
on
using such a procedure though. But it seems possible at least.