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 58CD40AA-6316-40B6-89C2-390D16FF5FA0@gmail.com
Whole thread Raw
In response to glibc updarte 2.31 to 2.38  (Paul Foerster <paul.foerster@gmail.com>)
List pgsql-general
Hi Peter,

> On 19 Sep 2024, at 19:43, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
>
> 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.)
>
> 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.
>
>        hp
>
> [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
buildsome 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




pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: glibc updarte 2.31 to 2.38
Next
From: Paul Foerster
Date:
Subject: Re: glibc updarte 2.31 to 2.38