| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alexey Shishkin <alexey(dot)shishkin(at)enterprisedb(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: OS system version upgrade (glibc / libicu version change) |
| Date: | 2026-11-16 15:21:01 |
| Message-ID: | 33876ecbca9932f1758b048ae9af9107bbeef55e.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, 2026-11-16 at 13:00 +0100, Alexey Shishkin wrote:
> We can grab the text for problem description from https://wiki.postgresql.org/wiki/Locale_data_changes
>
> Regarding finding the affected indexes, ready SQL queries for various PG versions are
> listed in the EDB KBA written by Peter Eisentraut.
> Or/and we can use amcheck as you suggested.
>
> Also we should mention that not only indexes can be affected by locale changes, but other objects
> like range-partitioned tables.
>
> One more thing to stress is that locale changes can happen during the lifecycle of the same major
> OS version, so any OS updates need to be verified for glibc changes.
>
> Pls. let me know how you would like to proceed.
Sure. You write a documentation patch, submit it to this list, and I am happy to
review it.
I suggest that the patch should not be too big. Code samples and instructions for repair
would be too much in my opinion. I'd say that the objective is to alert the reader to
the problem and tell him or her to rebuild affected indexes with REINDEX, and to use
amcheck to check if indexes are ok.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matemática A3K | 2026-11-17 03:00:37 | Re: Introductory docs-hacking task: Example markup |
| Previous Message | Alexey Shishkin | 2026-11-16 12:00:13 | Re: OS system version upgrade (glibc / libicu version change) |