| From: | Matthias Apitz <guru(at)unixarea(dot)de> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COLLATION update in 13.1 |
| Date: | 2025-03-24 05:57:18 |
| Message-ID: | Z-D0PoRbfrCufWdu@c720-1400094 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
El día lunes, febrero 24, 2025 a las 12:41:05p. m. +0100, Laurenz Albe escribió:
> Perhaps I need not say that, but ALTER COLLATION ... REFRESH VERSION only
> makes the warning disappear.
>
> If you want to avoid data corruption, rebuild all indexes on strings,
> then make the warning disappear.
>
> Yours,
> Laurenz Albe
One last question related to ALTER COLLATION ... In our clusters are also
the databases 'postgres', 'template0' and 'template1'. The latter we
never us and we CREATE new databases from 'template0'. Anyway, does it
make sense to ALTER COLLATION in these databases as well?
Thanks
matthias
--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
Annalena Baerbock: "We are fighting a war against Russia ..." (25.1.2023)
I, Matthias, I am not at war with Russia.
Я не воюю с Россией.
Ich bin nicht im Krieg mit Russland.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-03-24 06:27:21 | Re: COLLATION update in 13.1 |
| Previous Message | David G. Johnston | 2025-03-24 04:24:26 | Re: Best way to check if a table is empty |