Skip site navigation (1) Skip section navigation (2)

Re: default privileges wording

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: default privileges wording
Date: 2011-06-30 01:20:07
Message-ID: BANLkTikX3Ncq4S15=x3c1K8sd-MyBKCpzQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Itagaki TakahiroDate: 2011-06-30 01:26:52
Subject: Re: Adding Japanese README
Previous:From: David FetterDate: 2011-06-30 00:53:36
Subject: Re: default privileges wording

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group