public inbox for [email protected]  

help / color / mirror / Atom feed

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

El día lunes, marzo 24, 2025 a las 07:27:21a. m. +0100, Laurenz Albe escribió:

> 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.
> 
> ...

Thanks for your answer. Just for the record:

$ psql -Upostgres template0
Passwort für Benutzer postgres:
psql: FATAL:  database "template0" is not currently accepting connections
$

With 'template1' and 'postgres' it works fine.

	matthias

-- 
Matthias Apitz, ✉ [email protected], 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.

view thread (13+ messages)

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: <Z-ZDvVau16I_7txj@c720-1400094>

* 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