postgres.git / summary / log / commit / refs

commit    4ef048f34d2f9fed2e350bdc032da5a16907f99d
Author:   Daniel Gustafsson <dgustafsson@postgresql.org>
Date:     Wed Nov 12 16:04:35 2025 +0000

    doc: Document effects of ownership change on privileges
    
    Explicitly document that privileges are transferred along with the
    ownership. Backpatch to all supported versions since this behavior
    has always been present.
    
    Author: Laurenz Albe <laurenz.albe@cybertec.at>
    Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
    Reviewed-by: David G. Johnston <david.g.johnston@gmail.com>
    Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
    Reviewed-by: Josef Šimánek <josef.simanek@gmail.com>
    Reported-by: Gilles Parc <gparc@free.fr>
    Discussion: https://postgr.es/m/2023185982.281851219.1646733038464.JavaMail.root@zimbra15-e2.priv.proxad.net
    Backpatch-through: 14


 doc/src/sgml/ddl.sgml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 2333d8ef871..915ea10a860 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1646,6 +1646,9 @@ 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 a member of the owning role) and
    a member of the new owning role.
+   All object privileges of the old owner are transferred to the new owner
+   along with the ownership.
+
   </para>
 
   <para>


[parent: f8a0ea896556]