Thanks for your hint, Jeremy. But this does not work either: postgres=# SELECT collname, collversion FROM pg_collation where collname = 'de_DE.utf8'; collname | collversion ------------+------------- de_DE.utf8 | 2.38 (1 row)
postgres=# 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 AM Jeremy Schneider <schnei...@ardentperf.com> wrote: > On Mon, 24 Feb 2025 11:08:43 +0100 > Matthias Apitz <gurucub...@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 >
