Content-Type: text/plain;
	charset=us-ascii
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: <2bd05256-f031-41bf-9954-9ffaa6b19fc0@joeconway.com>
Date: Thu, 19 Sep 2024 20:32:18 +0200
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 pgsql-general list <pgsql-general@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <088E63DD-51AA-4720-AE38-E12A3C34ED9B@gmail.com>
References: <B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com>
 <1991352.1726758874@sss.pgh.pa.us>
 <FBFC83A0-55B2-4812-B9F3-38D42D7A9A7C@gmail.com>
 <2bd05256-f031-41bf-9954-9ffaa6b19fc0@joeconway.com>
To: Joe Conway <mail@joeconway.com>
Archived-At: <https://www.postgresql.org/message-id/088E63DD-51AA-4720-AE38-E12A3C34ED9B%40gmail.com>
Precedence: bulk

Hi Joe,

> On 19 Sep 2024, at 20:09, Joe Conway <mail@joeconway.com> wrote:
>=20
> See my thread-adjacent email, but suffice to say that if there are =
collation differences that do affect your tables/data, and you allow any =
inserts or updates, you may wind up with corrupted data (e.g. duplicate =
data in your otherwise unique indexes/primary keys).

Yes, I know that.

> For more examples about that see =
https://joeconway.com/presentations/glibc-SCaLE21x-2024.pdf

A very interesting PDF. Thanks very much.

> An potential alternative for you (discussed at the end of that =
presentation) would be to create a new branch based on your original =
SLES 15.5 glibc RPM equivalent to this:
>=20
> =
https://github.com/awslabs/compat-collation-for-glibc/tree/2.17-326.el7
>=20
> The is likely a non trivial amount of work involved (the port from the =
AL2 rpm to the RHEL7 rpm took me the better part of a couple of days), =
but once done your collation is frozen to the specific version you had =
on 15.5.

I'm not a developer. I have one machine which is equivalent to all other =
servers except that it has gcc, make and some other things for me to =
build PostgreSQL. I can't make the admins run a rpm on all servers. I =
can obviously put a library into the /path/2/postgres/software/lib64 =
directory but not into the system.

Also, my build server does not have internet access. So things like git =
clone would be an additional show stopper. Unfortunately, I'm pretty =
limited.

Cheers,
Paul