Doc: clarify that REASSIGN OWNED doesn't handle default privileges.

It doesn't touch regular privileges either, but only the latter was
explicitly stated.

Discussion: https://postgr.es/m/155348282848.9808.12629518043813943231@wrigleys.postgresql.org

diff --git a/doc/src/sgml/ref/drop_owned.sgml b/doc/src/sgml/ref/drop_owned.sgml
index 4c66da2b3409f94559e94a75380e8d14a4327232..09107bef64749bd758983ce0a0e36ec279983cdd 100644 (file)
--- a/doc/src/sgml/ref/drop_owned.sgml
+++ b/doc/src/sgml/ref/drop_owned.sgml
@@ -32,7 +32,7 @@ DROP OWNED BY { name | CURRENT_USER
    DROP OWNED drops all the objects within the current
    database that are owned by one of the specified roles. Any
    privileges granted to the given roles on objects in the current
-   database and on shared objects (databases, tablespaces) will also be
+   database or on shared objects (databases, tablespaces) will also be
    revoked.
   
  

diff --git a/doc/src/sgml/ref/reassign_owned.sgml b/doc/src/sgml/ref/reassign_owned.sgml
index 0fffd6088a9d20941dab38defe9e4d05de46ecb2..42f72a726fd1d964ca1366ba9355fc4d209534ed 100644 (file)
--- a/doc/src/sgml/ref/reassign_owned.sgml
+++ b/doc/src/sgml/ref/reassign_owned.sgml
@@ -88,9 +88,11 @@ REASSIGN OWNED BY { old_role | CURR
 
   
    The REASSIGN OWNED command does not affect any
-   privileges granted to the old_roles for
-   objects that are not owned by them.  Use DROP OWNED to
-   revoke such privileges.
+   privileges granted to
+   the old_roles on objects
+   that are not owned by them.  Likewise, it does not affect default
+   privileges created with ALTER DEFAULT PRIVILEGES.
+   Use DROP OWNED to revoke such privileges.