Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit1740510

Browse files
committed
Document that REVOKE doesn't remove all permissions if PUBLIC has permissions.
1 parentefa6783 commit1740510

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

‎doc/src/sgml/ref/revoke.sgml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/revoke.sgml,v 1.46 2007/10/30 19:43:30 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/revoke.sgml,v 1.47 2008/03/03 19:17:27 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -92,7 +92,10 @@ REVOKE [ ADMIN OPTION FOR ]
9292
<literal>PUBLIC</literal>. Thus, for example, revoking <literal>SELECT</> privilege
9393
from <literal>PUBLIC</literal> does not necessarily mean that all roles
9494
have lost <literal>SELECT</> privilege on the object: those who have it granted
95-
directly or via another role will still have it.
95+
directly or via another role will still have it. Similarly, revoking
96+
<literal>SELECT</> from a user might not prevent that user from using
97+
<literal>SELECT</> if <literal>PUBLIC</literal> or another membership
98+
role still has <literal>SELECT</> rights.
9699
</para>
97100

98101
<para>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp