From: | Matthias Apitz <gurucubano(at)googlemail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | COLLATION update in 13.1 |
Date: | 2025-02-24 10:08:43 |
Message-ID: | CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
When the Linux OS is updated, for example from SLES 15 SP5 to SP6, the
version of the glibc is sometimes updated, for example from 2.31 to 2.38.
For existing databases this gives on SQL a warning as:
user(at)rechner: $SC_SQL -Usisis sisis
WARNING: database "sisis" has a collation version mismatch
DETAIL: The database was created using collation version 2.31, but
the operating system provides version 2.38.
HINT: Rebuild all objects in this database that use the default
collation and run
ALTER DATABASE sisis REFRESH COLLATION VERSION, or build PostgreSQL
with the right library version.
...
This HINT works fine on 15.x and 16.x server versions.
On 13.1 it gives an SQL ERROR:
sisis=# ALTER DATABASE sisis REFRESH COLLATION VERSION;
ERROR: syntax error at or near "REFRESH"
LINE 1: ALTER DATABASE sisis REFRESH COLLATION VERSION;
What is the procedure on 13.1 to bring the external (glibc) version in sync
with. the used version in the PostgreSQL database?
Thanks
matthias
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Schneider | 2025-02-24 10:32:25 | Re: COLLATION update in 13.1 |
Previous Message | Dominique Devienne | 2025-02-24 09:46:17 | Keep specialized query pairs, or use single more general but more complex one |