Re: glibc updarte 2.31 to 2.38 - Mailing list pgsql-general

From Shaheed Haque
Subject Re: glibc updarte 2.31 to 2.38
Date
Msg-id CAHAc2jdOR=MRKW9=a7AUcFvViXOQDXKHp_FLzSLstLy=_voYqQ@mail.gmail.com
Whole thread Raw
In response to Re: glibc updarte 2.31 to 2.38  (Joe Conway <mail@joeconway.com>)
Responses Re: glibc updarte 2.31 to 2.38
Re: glibc updarte 2.31 to 2.38
List pgsql-general

I've been working on Unix-like systems for decades and though I thought I understood most of the issues to do with i18n/l10n, I've only just started using Postgres and I don't understand is why these changes ONLY seem to affect Postgres. Or is it more that it also affects text editors and the like, but we just tend to ignore that?

On Sun, 22 Sep 2024, 14:47 Joe Conway, <mail@joeconway.com> wrote:
On 9/21/24 15:19, Paul Foerster wrote:
> I already expressed the idea of changing all locales to ICU. The
> problem there is that I'd have to create new instances and then move
> each database individually. I wish I could convert already running
> databases… This also takes time. Still, I think I'm going to try
> this route. It's always a gamble if reindexing is needed or not with
> any glibc change.


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.


--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com


pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: glibc updarte 2.31 to 2.38
Next
From: Ron Johnson
Date:
Subject: Re: glibc updarte 2.31 to 2.38