Date: Wed, 24 Jan 2024 11:08:21 +0100 (CET)
From: gparc@free.fr
To: pgsql-docs <pgsql-docs@lists.postgresql.org>
Message-ID: <1712096587.208766558.1706090901073.JavaMail.zimbra@free.fr>
In-Reply-To: 
 <2023185982.281851219.1646733038464.JavaMail.root@zimbra15-e2.priv.proxad.net>
References: 
 <2023185982.281851219.1646733038464.JavaMail.root@zimbra15-e2.priv.proxad.net>
Subject: Re: SQL command : ALTER DATABASE OWNER TO
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: SQL command : ALTER DATABASE OWNER TO
Thread-Index: wS+LUhduZQeXdTPK15YQG1LRXIwTzg==
Archived-At: 
 <https://www.postgresql.org/message-id/1712096587.208766558.1706090901073.JavaMail.zimbra%40free.fr>
Precedence: bulk

Hello,

as one of my colleagues fell into the same trap
I repeat my request for correction of the documentation on this subject.

Many thanks in advance

Regards
Gilles

----- Mail original -----
De: "gparc" <gparc@free.fr>
=C3=80: "pgsql-docs" <pgsql-docs@lists.postgresql.org>
Envoy=C3=A9: Mardi 8 Mars 2022 10:50:38
Objet: SQL command : ALTER DATABASE OWNER TO

Hello,

for this "ALTER DATABASE" form, it should be mentioned that after execution=
 of the command,
the old database owner loses all his privileges on it (even connection) alt=
hough it might
still owns schemas or objects (tables, index,...) inside it.

Thanks in advance to add this important precision.

Regards
Gilles