Date: Wed, 24 Jan 2024 15:40:20 +0100 (CET)
From: gparc@free.fr
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
	pgsql-docs <pgsql-docs@lists.postgresql.org>
Message-ID: <1327973565.212682013.1706107220766.JavaMail.zimbra@free.fr>
In-Reply-To: <EC6A3402-8271-4EA7-B6BA-1CEFEA96C749@yesql.se>
References: 
 <2023185982.281851219.1646733038464.JavaMail.root@zimbra15-e2.priv.proxad.net>
 <1712096587.208766558.1706090901073.JavaMail.zimbra@free.fr>
 <bd4c8b8e88548d6e08220196a02c17d4fa5d2124.camel@cybertec.at>
 <EC6A3402-8271-4EA7-B6BA-1CEFEA96C749@yesql.se>
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: ExIuC/BKUOTnXRN66y0trrvJtBzeag==
Archived-At: 
 <https://www.postgresql.org/message-id/1327973565.212682013.1706107220766.JavaMail.zimbra%40free.fr>
Precedence: bulk


Hello,

maybe a misunderstanding of my part, but your proposed modification doesn't=
 matched
with the current behaviour of the command as precisely the object privilege=
s of the old owner are **NOT** transferred
to the new owner along with the ownership

Regards
Gilles

----- Mail original -----
De: "Daniel Gustafsson" <daniel@yesql.se>
=C3=80: "Laurenz Albe" <laurenz.albe@cybertec.at>
Cc: "gparc" <gparc@free.fr>, "pgsql-docs" <pgsql-docs@lists.postgresql.org>
Envoy=C3=A9: Mercredi 24 Janvier 2024 15:26:22
Objet: Re: SQL command : ALTER DATABASE OWNER TO

> On 24 Jan 2024, at 15:23, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>=20
> On Wed, 2024-01-24 at 11:08 +0100, gparc@free.fr wrote:
>> for this "ALTER DATABASE" form, it should be mentioned that after execut=
ion of the command,
>> the old database owner loses all his privileges on it (even connection) =
although it might
>> still owns schemas or objects (tables, index,...) inside it.
>>=20
>> Thanks in advance to add this important precision.
>=20
> How about this:
>=20
> diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
> index 4044f0908f..44042f863c 100644
> --- a/doc/src/sgml/ddl.sgml
> +++ b/doc/src/sgml/ddl.sgml
> @@ -1891,6 +1891,8 @@ ALTER TABLE <replaceable>table_name</replaceable> O=
WNER TO <replaceable>new_owne
>    Superusers can always do this; ordinary roles can only do it if they a=
re
>    both the current owner of the object (or inherit the privileges of the
>    owning role) and able to <literal>SET ROLE</literal> to the new owning=
 role.
> +   All object privileges of the old owner are transferred to the new own=
er
> +   along with the ownership.
>   </para>

Doesn't seem unreasonable to me, it won't make the docs harder to read and =
use
for experienced users while it may make them easier to follow for new users=
.

--
Daniel Gustafsson