| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Matthias Apitz <guru(at)unixarea(dot)de> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COLLATION update in 13.1 |
| Date: | 2025-03-24 06:27:21 |
| Message-ID: | c1f6a6487f3b1ffb1a761308a9e77b9aa7d6044f.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cars Jeeva | 2025-03-24 14:18:27 | Today Page is not accessible - postgresql-15.spec |
| Previous Message | Matthias Apitz | 2025-03-24 05:57:18 | Re: COLLATION update in 13.1 |