Re: COLLATION update in 13.1
От | Laurenz Albe |
---|---|
Тема | Re: COLLATION update in 13.1 |
Дата | |
Msg-id | c1f6a6487f3b1ffb1a761308a9e77b9aa7d6044f.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: COLLATION update in 13.1 (Matthias Apitz <guru@unixarea.de>) |
Ответы |
Re: COLLATION update in 13.1
|
Список | pgsql-general |
On Mon, 2025-03-24 at 06:57 +0100, Matthias Apitz wrote: > 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. > > 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? I would say so, yes. At least on the template you are using for new databases. By the way, your signature makes Google move your e-mail to "spam". Just saying. Yours, Laurenz Albe
В списке pgsql-general по дате отправления: