public inbox for [email protected]  

help / color / mirror / Atom feed
From: Alexey Shishkin <[email protected]>
To: [email protected]
Subject: Re: OS system version upgrade (glibc / libicu version change)
Date: Tue, 17 Feb 2026 15:33:28 +0100
Message-ID: <CALVdoE78O7Ksm+1ySLCv=Bs_-O5hHyQfXHEMaNC3dPP1t2WSQw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Hi, Team !

Any ideas regarding my proposal ?

My recent experience is about the customers migrating from RHEL8 to RHEL10
and from SLES12 to SLES15 and they don't have the answers from PostgreSQL
documentation.


best regards,

Alexey Shishkin





*Alexey Shishkin*

Technical Account Manager

EDB Software GmbH

[email protected]



www.enterprisedb.com <https://enterprisedb.com/;




On Mon, Feb 2, 2026 at 10:08 AM PG Doc comments form <[email protected]>
wrote:

> 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
>
>


view thread (2+ messages)

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: OS system version upgrade (glibc / libicu version change)
  In-Reply-To: <CALVdoE78O7Ksm+1ySLCv=Bs_-O5hHyQfXHEMaNC3dPP1t2WSQw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox