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: <20240919174349.grrz4w25jmxfk77a@hjp.at>
Date: Thu, 19 Sep 2024 20:12:13 +0200
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <58CD40AA-6316-40B6-89C2-390D16FF5FA0@gmail.com>
References: <B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com>
 <20240919174349.grrz4w25jmxfk77a@hjp.at>
To: "Peter J. Holzer" <hjp-pgsql@hjp.at>
Archived-At: <https://www.postgresql.org/message-id/58CD40AA-6316-40B6-89C2-390D16FF5FA0%40gmail.com>
Precedence: bulk

Hi Peter,

> On 19 Sep 2024, at 19:43, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
>=20
> I wrote a small script[1] which prints all unicode code points and a =
few
> selected[2] longer strings in order. If you run that before and after
> the upgrade and the output doesn't change, you are probably be fine.
> (It checks only the default collation, though: If you have indexes =
using
> a different collation you would have to modify the script =
accordingly.)
>=20
> If there are differences, closer inspection might show that the =
changes
> don't affect you. But I would reindex all indexes on text (etc.) =
columns
> just to be sure.
>=20
>        hp
>=20
> [1] https://git.hjp.at:3000/hjp/pgcollate
> [2] The selection is highly subjective and totally unscientific.
>    Additions are welcome.

I'm not a Python specialist but I take it that the script need psycopg2, =
which we probably don't have. So I'd have to build some sort of venv =
around that like I had to do to get Patroni working on our systems.

Well, we'll see.

Thanks for this script.

Cheers,
Paul