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