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

Add a note about the difference between Postgres' treatment of the rights

Browse Source 
of an object owner and the SQL spec's treatment of these rights.
This commit is contained in:
Tom Lane
2004-09-01 04:13:11 +00:00
parent 33f395eada
commit 3ff8cc45ad
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 PostgreSQL documentation
--> -->
@ -403,6 +403,18 @@ GRANT ALL PRIVILEGES ON kinds TO manuel;
one object per command. one object per command.
</para> </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> <para>
The SQL standard allows setting privileges for individual columns The SQL standard allows setting privileges for individual columns
within a table: within a table: