From 5f1b32ddf826550d65dd6e84b965b6a98589ad19 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Sat, 12 Sep 2009 16:26:06 +0000
Subject: [PATCH] Improve GRANT reference page's description of object
 ownership privileges by mentioning the possibility of granting membership in
 the owning role.

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

diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index ceda72c141d..fe927e0ffe2 100644
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.74 2009/01/22 20:15:59 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.75 2009/09/12 16:26:06 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -121,9 +121,14 @@ GRANT <replaceable class="PARAMETER">role</replaceable> [, ...] TO <replaceable
    (usually the user that created it),
    as the owner has all privileges by default.  (The owner could,
    however, choose to revoke some of his own privileges for safety.)
-   The right to drop an object, or to alter its definition in any way is
-   not described by a grantable privilege; it is inherent in the owner,
-   and cannot be granted or revoked.  The owner implicitly has all grant
+  </para>
+
+  <para>
+   The right to drop an object, or to alter its definition in any way, is
+   not treated as a grantable privilege; it is inherent in the owner,
+   and cannot be granted or revoked.  (However, a similar effect can be
+   obtained by granting or revoking membership in the role that owns
+   the object; see below.)  The owner implicitly has all grant
    options for the object, too.
   </para>
 
-- 
2.39.5