database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-29 13:56:47 +03:00
Code

Clarify per suggestion from Bruno Wolff.

Browse Source
This commit is contained in:
Tom Lane 2001-11-28 15:39:49 +00:00
parent d2f608251e
commit 9d596e0e3e
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/user-manag.sgml
View File

@ -162,7 +162,7 @@ GRANT UPDATE ON accounts TO joe;
GRANT SELECT ON accounts TO GROUP staff; GRANT SELECT ON accounts TO GROUP staff;
</programlisting> </programlisting>
The special <quote>user</quote> name <literal>PUBLIC</literal> can 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 <literal>ALL</literal> in place of a specific privilege specifies that all
privileges will be granted. privileges will be granted.
</para> </para>
@ -173,8 +173,12 @@ GRANT SELECT ON accounts TO GROUP staff;
<programlisting> <programlisting>
REVOKE ALL ON accounts FROM PUBLIC; REVOKE ALL ON accounts FROM PUBLIC;
</programlisting> </programlisting>
The special privileges of the table owner are always implicit The special privileges of the table owner (i.e., the right to do
and cannot be granted or revoked. <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> </para>
</sect1> </sect1>