diff options
author | Tom Lane | 2001-11-28 15:39:49 +0000 |
---|---|---|
committer | Tom Lane | 2001-11-28 15:39:49 +0000 |
commit | 9d596e0e3eed6b6d244d104775df091a65aa310f (patch) | |
tree | 1d0b8e26c7fa87e570d6ea90cebd626ef8169d28 | |
parent | d2f608251e621dbe4aff363154b3a27123cc3814 (diff) |
Clarify per suggestion from Bruno Wolff.
-rw-r--r-- | doc/src/sgml/user-manag.sgml | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml index cdfeaea31e7..d2e7fff96d0 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> |