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

From Paul Foerster
Subject Re: glibc updarte 2.31 to 2.38
Date
Msg-id DA5B67BD-F5EB-4566-B8C4-AFBBB0753CF4@gmail.com
Whole thread Raw
In response to glibc updarte 2.31 to 2.38  (Paul Foerster <paul.foerster@gmail.com>)
Responses Re: glibc updarte 2.31 to 2.38
List pgsql-general
Hi Peter,

> On 21 Sep 2024, at 00:33, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
>
> I don't use SLES but I would expect it to have an RPM for it.
>
> If you have any test machine which you can upgrade before the production
> servers (and given the amount of data and availability requirements you
> have, I really hope you do) you should be set.

One of our admins did me a favor and upgraded my build server ahead of schedule. So I can both test our current
PostgreSQLversion as well as rebuild it if necessary. 

I can't test all of our data. That'd take quite a few months or more. I just can try to identify some crucial databases
andcolumns. When those tests are done, I can only pray and hope for the best. 

I already expressed the idea of changing all locales to ICU. The problem there is that I'd have to create new instances
andthen move each database individually. I wish I could convert already running databases… This also takes time. Still,
Ithink I'm going to try this route. It's always a gamble if reindexing is needed or not with any glibc change. 

Cheers,
Paul


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: How batch processing works
Next
From: Justin
Date:
Subject: Re: Logical Replication Delay