| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | alexey(dot)shishkin(at)enterprisedb(dot)com |
| Subject: | OS system version upgrade (glibc / libicu version change) |
| Date: | 2026-02-02 09:07:41 |
| Message-ID: | 177002326159.803.1983703962002247846@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/collation.html
Description:
Hi, Team !
It looks like the PostgreSQL documentation doesn't explain the customers
what to do with PostgreSQL in case of OS system version upgrade or/and glibc
/ libicu version change.
There're many links/blogs available where the required actions are
explained.
https://knowledge.enterprisedb.com/hc/en-us/articles/13520015051420-glibc-locale-data-changes
https://www.crunchydata.com/blog/postgres-migration-pitstop-collations
https://wiki.postgresql.org/wiki/Locale_data_changes
The thing is some of the recommendations are not complete or/and not
up-to-date.
I see a lot of confusion in the field about this topic, because PostgreSQL
users don't have the 'official recommendations' from the PostgreSQL
community.
So, my proposal to dedicate a chapter in the PostgreSQL documentation about
the topic.
best regards
Alexey Shishkin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hoda Salim | 2026-02-02 15:05:03 | [PATCH] docs: document N'...' national character string literal syntax |
| Previous Message | Fujii Masao | 2026-01-23 10:21:51 | Placement of synchronized_standby_slots description in config.sgml |