Skip to content
Snippets Groups Projects
Commit 17405109 authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Document that REVOKE doesn't remove all permissions if PUBLIC has permissions.

parent efa67833
No related branches found
No related tags found
No related merge requests found
<!--
$PostgreSQL: pgsql/doc/src/sgml/ref/revoke.sgml,v 1.46 2007/10/30 19:43:30 tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/ref/revoke.sgml,v 1.47 2008/03/03 19:17:27 momjian Exp $
PostgreSQL documentation
-->
......@@ -92,7 +92,10 @@ REVOKE [ ADMIN OPTION FOR ]
<literal>PUBLIC</literal>. Thus, for example, revoking <literal>SELECT</> privilege
from <literal>PUBLIC</literal> does not necessarily mean that all roles
have lost <literal>SELECT</> privilege on the object: those who have it granted
directly or via another role will still have it.
directly or via another role will still have it. Similarly, revoking
<literal>SELECT</> from a user might not prevent that user from using
<literal>SELECT</> if <literal>PUBLIC</literal> or another membership
role still has <literal>SELECT</> rights.
</para>
<para>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment