| 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-28 07:17:04 |
| Message-ID: | f39b5db0281e0d026579ca9ed147905d845ee9d5.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2025-03-28 at 07:37 +0100, Matthias Apitz wrote:
> 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.
>
> $ psql -Upostgres template0
> Passwort für Benutzer postgres:
> psql: FATAL: database "template0" is not currently accepting connections
> $
>
> With 'template1' and 'postgres' it works fine.
You'd have to temporarily allow connections and reset it once you are done.
ALTER DATABASE template0 ALLOW_CONNECTIONS TRUE;
\c template0
ALTER COLLATION ... REFRESH VERSION;
ALTER DATABASE template0 ALLOW_CONNECTIONS FALSE;
\q
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moreno Andreo | 2025-03-28 12:38:26 | BTREE index: field ordering |
| Previous Message | Laurenz Albe | 2025-03-28 07:12:32 | Re: Trying to dynamically create a procedure |