Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\))
Subject: Re: glibc updarte 2.31 to 2.38
From: Paul Foerster <paul.foerster@gmail.com>
In-Reply-To: <20240920223316.muvdgqekzh6dvcii@hjp.at>
Date: Sat, 21 Sep 2024 21:19:32 +0200
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA5B67BD-F5EB-4566-B8C4-AFBBB0753CF4@gmail.com>
References: <B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com>
 <20240919174349.grrz4w25jmxfk77a@hjp.at>
 <58CD40AA-6316-40B6-89C2-390D16FF5FA0@gmail.com>
 <20240920223316.muvdgqekzh6dvcii@hjp.at>
To: "Peter J. Holzer" <hjp-pgsql@hjp.at>
Archived-At: <https://www.postgresql.org/message-id/DA5B67BD-F5EB-4566-B8C4-AFBBB0753CF4%40gmail.com>
Precedence: bulk

Hi Peter,

> On 21 Sep 2024, at 00:33, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
>=20
> I don't use SLES but I would expect it to have an RPM for it.
>=20
> 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 PostgreSQL version 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 and columns. 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 and then move each =
database individually. I wish I could convert already running =
databases=E2=80=A6 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.

Cheers,
Paul=