public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: Matthias Apitz <[email protected]>
Cc: [email protected]
Subject: Re: COLLATION update in 13.1
Date: Mon, 24 Mar 2025 07:27:21 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <Z-D0PoRbfrCufWdu@c720-1400094>
References: <CAHzebO-2qy2RkrhTvqPs8=6Ju_6-7C=MSumVMZxTs7zRYp-6mA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<Z-D0PoRbfrCufWdu@c720-1400094>

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

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: COLLATION update in 13.1
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox