| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: glibc updarte 2.31 to 2.38 |
| Date: | 2024-09-22 16:53:58 |
| Message-ID: | 5b0f58e4-f0cd-4a27-91bd-9a83a65c86d5@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 9/22/24 09:48, Paul Förster wrote:
> Hi Joe
>
>> On 22. Sep, 2024, at 15:47, Joe Conway <mail(at)joeconway(dot)com> wrote:
>>
>> Note that moving to ICU might improve things, but there are similar potential issues with ICU as well. The trick there would be to get your OS distro provider to maintain the same ICU version across major versions of the distro, which is not the case currently. Nor does the PGDG repo do that.
>
> Then I strongly suggest that the PostgreSQL developers develop a fail safe sorting mechanism that holds for generations of locale changes.
https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-HIGHLIGHTS
Add a builtin platform-independent collation provider (Jeff Davis)
This supports C and C.UTF-8 collations.
>
> Cheers,
> Paul
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2024-09-22 18:44:49 | Re: glibc updarte 2.31 to 2.38 |
| Previous Message | Paul Förster | 2024-09-22 16:52:30 | Re: glibc updarte 2.31 to 2.38 |