From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Thomas Michael Engelke <thomas.engelke@posteo.de>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: ICU Collations and Collation Updates
Date: Mon, 14 Apr 2025 19:18:46 +0200
Message-ID: <20250414191846.39b9415e@karst> (raw)
In-Reply-To: <1257278.1744641400@sss.pgh.pa.us>
References: <8ed41c50ba6c5322296b869e497c1b5573853b54.camel@posteo.de>
<d477c1faf35bad99fe550c8c4c1954ffa076ccfd.camel@cybertec.at>
<1257278.1744641400@sss.pgh.pa.us>
Le Mon, 14 Apr 2025 10:36:40 -0400,
Tom Lane <tgl@sss.pgh.pa.us> a écrit :
[…]
> 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#31c548587bc98686e010e500a...
It's probably another level of maintenance to provide a stable UTF8 collation
using such a procedure though. But it seems possible at least.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: jgdr@dalibo.com, tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, thomas.engelke@posteo.de, pgsql-general@lists.postgresql.org
Subject: Re: ICU Collations and Collation Updates
In-Reply-To: <20250414191846.39b9415e@karst>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox