From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 28 Nov 2001 15:39:49 +0000 (+0000)
Subject: Clarify per suggestion from Bruno Wolff.
X-Git-Tag: REL7_2_BETA4~110
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9d596e0e3eed6b6d244d104775df091a65aa310f;p=postgresql

Clarify per suggestion from Bruno Wolff.
---

diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
index cdfeaea31e..d2e7fff96d 100644
--- a/doc/src/sgml/user-manag.sgml
+++ b/doc/src/sgml/user-manag.sgml
@@ -162,7 +162,7 @@ GRANT UPDATE ON accounts TO joe;
 GRANT SELECT ON accounts TO GROUP staff;
 </programlisting>
    The special <quote>user</quote> name <literal>PUBLIC</literal> can
-   be used to grant a privilege to every user on the system. Using
+   be used to grant a privilege to every user on the system. Writing
    <literal>ALL</literal> in place of a specific privilege specifies that all
    privileges will be granted.
   </para>
@@ -173,8 +173,12 @@ GRANT SELECT ON accounts TO GROUP staff;
 <programlisting>
 REVOKE ALL ON accounts FROM PUBLIC;
 </programlisting>
-   The special privileges of the table owner are always implicit
-   and cannot be granted or revoked.
+   The special privileges of the table owner (i.e., the right to do
+   <command>DROP</>, <command>GRANT</>, <command>REVOKE</>, etc)
+   are always implicit in being the owner,
+   and cannot be granted or revoked.  But the table owner can choose
+   to revoke his own ordinary privileges, for example to make a
+   table read-only for himself as well as others.
   </para>
  </sect1>