MIME-Version: 1.0
References: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>
 <20250224023225.197cac12@ardentperf.com>
In-Reply-To: <20250224023225.197cac12@ardentperf.com>
From: Matthias Apitz <gurucubano@googlemail.com>
Date: Mon, 24 Feb 2025 12:32:57 +0100
Message-ID: <CAHzebO92PxW=e2FLN=ZSkMEvfoS+c-b9YKQNgj0Y3hj21pMw+A@mail.gmail.com>
Subject: Re: COLLATION update in 13.1
To: Jeremy Schneider <schneider@ardentperf.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000004cd6ad062ee1b4f7"
Archived-At: <https://www.postgresql.org/message-id/CAHzebO92PxW%3De2FLN%3DZSkMEvfoS%2Bc-b9YKQNgj0Y3hj21pMw%2BA%40mail.gmail.com>
Precedence: bulk

--0000000000004cd6ad062ee1b4f7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for your hint, Jeremy. But this does not work either:

postgres=3D# SELECT collname, collversion FROM pg_collation where collname =
=3D
'de_DE.utf8';
  collname  | collversion
------------+-------------
 de_DE.utf8 | 2.38
(1 row)

postgres=3D# ALTER COLLATION de_DE.utf8 REFRESH VERSION;
ERROR:  schema "de_de" does not exist

What do I wrong?

Matthia

On Mon, Feb 24, 2025 at 11:32=E2=80=AFAM Jeremy Schneider <schneider@ardent=
perf.com>
wrote:

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

--0000000000004cd6ad062ee1b4f7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks for your hint, Jeremy. But this does not work =
either:</div><div><br></div><div>postgres=3D# SELECT collname, collversion =
FROM pg_collation where collname =3D &#39;de_DE.utf8&#39;;<br>=C2=A0 collna=
me =C2=A0| collversion<br>------------+-------------<br>=C2=A0de_DE.utf8 | =
2.38<br>(1 row)<br><br>postgres=3D# ALTER COLLATION de_DE.utf8 REFRESH VERS=
ION;<br>ERROR: =C2=A0schema &quot;de_de&quot; does not exist</div><div><br>=
</div><div>What do I wrong?</div><div><br></div><div>Matthia</div></div><br=
><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D=
"gmail_attr">On Mon, Feb 24, 2025 at 11:32=E2=80=AFAM Jeremy Schneider &lt;=
<a href=3D"mailto:schneider@ardentperf.com">schneider@ardentperf.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon,=
 24 Feb 2025 11:08:43 +0100<br>
Matthias Apitz &lt;<a href=3D"mailto:gurucubano@googlemail.com" target=3D"_=
blank">gurucubano@googlemail.com</a>&gt; wrote:<br>
<br>
&gt; <br>
&gt; What is the procedure on 13.1 to bring the external (glibc) version<br=
>
&gt; in sync with. the used version in the PostgreSQL database?<br>
<br>
If I recall correctly, between versions 10 and 14 you need to use ALTER<br>
COLLATION name REFRESH VERSION on every collation where there&#39;s a<br>
version mismatch. (This can happen with ICU collations since version 10,<br=
>
and with glibc collations since version 13.)<br>
<br>
I only know of a small number of changes between glibc versions 2.31 and<br=
>
2.38 ~ I suspect you already know to look out for glibc 2.28 which was<br>
the crazy one. (SLE15 Service Pack 3.) Most databases would be<br>
corrupted by that update, and running &quot;refresh version&quot; would sim=
ply<br>
stop the warnings without fixing the corruption.<br>
<br>
-Jeremy<br>
</blockquote></div>

--0000000000004cd6ad062ee1b4f7--