Re: default privileges wording

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Fetter <david(at)fetter(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: default privileges wording
Date: 2011-06-30 01:54:59
Message-ID: 4E0BD773.10301@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/29/2011 09:20 PM, Robert Haas wrote:
> On Wed, Jun 29, 2011 at 8:53 PM, David Fetter<david(at)fetter(dot)org> wrote:
>> How about this?
>>
>> PostgreSQL grants some types of objects some default privileges to
>> PUBLIC. Tables, columns, schemas and tablespaces grant no privileges
>> to PUBLIC by default. For other types, the default privileges granted
>> to PUBLIC are as follows: CONNECT and CREATE TEMP TABLE for databases;
>> EXECUTE privilege for functions; and USAGE privilege for languages.
>> The object owner can, of course, REVOKE both default and expressly
>> granted privileges.
> That looks pretty good to me. I'd probably say "grants default
> privileges on some types of objects" rather than "grants some types of
> objects default privileges", but YMMV.

Yeah, that sounds good. The second sentence reads oddly to me - it's not
the objects that are doing (or not doing) the granting; rather they are
the subjects of the (lack of) granted privileges. Maybe we should say:

"No privileges are granted to PUBLIC by default on tables, columns,
schemas or tablespaces."

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-06-30 01:55:53 Re: time-delayed standbys
Previous Message Josh Berkus 2011-06-30 01:54:19 Re: time-delayed standbys