database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Improve GRANT reference page's description of object ownership

Browse Source 
privileges by mentioning the possibility of granting membership in
the owning role.
This commit is contained in:
Tom Lane
2009-09-12 16:26:06 +00:00
parent 325aeb4a65
commit 5f1b32ddf8
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/ref/grant.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.74 2009/01/22 20:15:59 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.75 2009/09/12 16:26:06 tgl Exp $
PostgreSQL documentation PostgreSQL documentation
--> -->
@ -121,9 +121,14 @@ GRANT <replaceable class="PARAMETER">role</replaceable> [, ...] TO <replaceable
(usually the user that created it), (usually the user that created it),
as the owner has all privileges by default. (The owner could, as the owner has all privileges by default. (The owner could,
however, choose to revoke some of his own privileges for safety.) however, choose to revoke some of his own privileges for safety.)
The right to drop an object, or to alter its definition in any way is </para>
not described by a grantable privilege; it is inherent in the owner,
and cannot be granted or revoked. The owner implicitly has all grant <para>
The right to drop an object, or to alter its definition in any way, is
not treated as a grantable privilege; it is inherent in the owner,
and cannot be granted or revoked. (However, a similar effect can be
obtained by granting or revoking membership in the role that owns
the object; see below.) The owner implicitly has all grant
options for the object, too. options for the object, too.
</para> </para>