From 60bd2b1941c6211e973770e69cfa33367cc5db48 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 5 Apr 2010 01:58:03 +0000
Subject: Arrange to remove pg_default_acl entries completely if their ACL
 setting is changed to match the hard-wired default.  This avoids accumulating
 useless catalog entries, and also provides a path for dropping the owning
 role without using DROP OWNED BY.  Per yesterday's complaint from Jaime
 Casanova, the need to use DROP OWNED BY for that is less than obvious, so
 providing this alternative method might save some user frustration.

---
 doc/src/sgml/ref/alter_default_privileges.sgml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/alter_default_privileges.sgml b/doc/src/sgml/ref/alter_default_privileges.sgml
index 4f0b0bc9c83..2099c3471ec 100644
--- a/doc/src/sgml/ref/alter_default_privileges.sgml
+++ b/doc/src/sgml/ref/alter_default_privileges.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_default_privileges.sgml,v 1.4 2010/04/03 21:46:59 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_default_privileges.sgml,v 1.5 2010/04/05 01:58:03 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -150,9 +150,10 @@ REVOKE [ GRANT OPTION FOR ]
   </para>
 
   <para>
-   If you wish to drop a role for which the default privileges have ever been
-   altered, it is necessary to use <command>DROP OWNED BY</> first,
-   to get rid of the default privileges entry for the role.
+   If you wish to drop a role for which the default privileges have been
+   altered, it is necessary to reverse the changes in its default privileges
+   or use <command>DROP OWNED BY</> to get rid of the default privileges entry
+   for the role.
   </para>
  </refsect1>
 
-- 
cgit v1.2.3