| From: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: glibc updarte 2.31 to 2.38 |
| Date: | 2024-09-19 18:12:13 |
| Message-ID: | 58CD40AA-6316-40B6-89C2-390D16FF5FA0@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Peter,
> On 19 Sep 2024, at 19:43, Peter J. Holzer <hjp-pgsql(at)hjp(dot)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 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Foerster | 2024-09-19 18:32:18 | Re: glibc updarte 2.31 to 2.38 |
| Previous Message | Joe Conway | 2024-09-19 18:09:38 | Re: glibc updarte 2.31 to 2.38 |