| From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Thomas Michael Engelke <thomas(dot)engelke(at)posteo(dot)de>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ICU Collations and Collation Updates |
| Date: | 2025-04-14 17:18:46 |
| Message-ID: | 20250414191846.39b9415e@karst |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le Mon, 14 Apr 2025 10:36:40 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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:
It's probably another level of maintenance to provide a stable UTF8 collation
using such a procedure though. But it seems possible at least.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Foerster | 2025-04-14 17:24:29 | Re: ICU Collations and Collation Updates |
| Previous Message | Dimitrios Apostolou | 2025-04-14 16:09:30 | Re: TRUNCATE ONLY with foreign keys and triggers disabled |