public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeremy Schneider <[email protected]>
To: Matthias Apitz <[email protected]>
Cc: [email protected]
Subject: Re: COLLATION update in 13.1
Date: Mon, 24 Feb 2025 02:32:25 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>
References: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>

On Mon, 24 Feb 2025 11:08:43 +0100
Matthias Apitz <[email protected]> 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

view thread (13+ messages)  latest in thread

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], [email protected]
  Subject: Re: COLLATION update in 13.1
  In-Reply-To: <[email protected]>

* 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