Re: SQL command : ALTER DATABASE OWNER TO

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: gparc(at)free(dot)fr, pgsql-docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: SQL command : ALTER DATABASE OWNER TO
Date: 2024-01-24 14:23:21
Message-ID: bd4c8b8e88548d6e08220196a02c17d4fa5d2124.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, 2024-01-24 at 11:08 +0100, gparc(at)free(dot)fr wrote:
> 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) although it might
> still owns schemas or objects (tables, index,...) inside it.
>
> Thanks in advance to add this important precision.

How about this:

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> OWNER TO <replaceable>new_owne
Superusers can always do this; ordinary roles can only do it if they are
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 owner
+ along with the ownership.
</para>

<para>

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Daniel Gustafsson 2024-01-24 14:26:22 Re: SQL command : ALTER DATABASE OWNER TO
Previous Message gparc 2024-01-24 10:08:21 Re: SQL command : ALTER DATABASE OWNER TO