aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/ref/grant.sgml14
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index 9ea480c57a3..d6a6ef94b6f 100644
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.42 2004/08/07 20:44:50 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.43 2004/09/01 04:13:11 tgl Exp $
PostgreSQL documentation
-->
@@ -404,6 +404,18 @@ GRANT ALL PRIVILEGES ON kinds TO manuel;
</para>
<para>
+ <productname>PostgreSQL</productname> allows an object owner to revoke his
+ own ordinary privileges: for example, a table owner can make the table
+ read-only to himself by revoking his own INSERT, UPDATE, and DELETE
+ privileges. This is not possible according to the SQL standard. The
+ reason is that <productname>PostgreSQL</productname> treats the owner's
+ privileges as having been granted by the owner to himself; therefore he
+ can revoke them too. In the SQL standard, the owner's privileges are
+ granted by an assumed entity <quote>_SYSTEM</>. Not being
+ <quote>_SYSTEM</>, the owner cannot revoke these rights.
+ </para>
+
+ <para>
The SQL standard allows setting privileges for individual columns
within a table: