From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | default privileges wording |
Date: | 2011-06-29 15:21:12 |
Message-ID: | 4E0B42E8.3090905@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I was just reading the docs on default privileges, and they say this:
Depending on the type of object, the initial default privileges
might include granting some privileges to PUBLIC. The default is no
public access for tables, columns, schemas, and tablespaces; CONNECT
privilege and TEMP table creation privilege for databases; EXECUTE
privilege for functions; and USAGE privilege for languages. The
object owner can of course revoke these privileges.
I had to read it several times before I understood it properly, so I'm
not terribly happy with it. I'm thinking of revising it slightly like this:
Depending on the type of object, the initial default privileges
might include granting some privileges to PUBLIC, including CONNECT
privilege and TEMP table creation privilege for databases, EXECUTE
privilege for functions, and USAGE privilege for languages. For
tables, columns, schemas and tablespaces the default is no public
access. The object owner can of course revoke any default PUBLIC
privileges.
That seems clearer to me, but maybe other people can make it clearer still.
Comments?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2011-06-29 15:41:49 | Re: Range Types, constructors, and the type system |
Previous Message | Merlin Moncure | 2011-06-29 15:11:24 | Re: Process local hint bit cache |