Date: Mon, 24 Feb 2025 02:32:25 -0800
From: Jeremy Schneider <schneider@ardentperf.com>
To: Matthias Apitz <gurucubano@googlemail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: COLLATION update in 13.1
Message-ID: <20250224023225.197cac12@ardentperf.com>
In-Reply-To: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>
References: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/20250224023225.197cac12%40ardentperf.com>
Precedence: bulk

On Mon, 24 Feb 2025 11:08:43 +0100
Matthias Apitz <gurucubano@googlemail.com> wrote:

> 
> What is the procedure on 13.1 to bring the external (glibc) version
> in sync with. the used version in the PostgreSQL database?

If I recall correctly, between versions 10 and 14 you need to use ALTER
COLLATION name REFRESH VERSION on every collation where there's a
version mismatch. (This can happen with ICU collations since version 10,
and with glibc collations since version 13.)

I only know of a small number of changes between glibc versions 2.31 and
2.38 ~ I suspect you already know to look out for glibc 2.28 which was
the crazy one. (SLE15 Service Pack 3.) Most databases would be
corrupted by that update, and running "refresh version" would simply
stop the warnings without fixing the corruption.

-Jeremy