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

Re: BUG #6021: There is no difference between default and empty access privileges with \dp

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: gszpetkowski(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6021: There is no difference between default and empty access privileges with \dp
Date: 2011-05-15 20:01:16
Message-ID: BANLkTikGc3gJLkHSAbzku5KipPtUq9Ep2w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, May 12, 2011 at 6:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "psql \dp showing empty Access privileges column for {}" <gszpetkowski(at)gmail(dot)com> writes:
>> Description:        There is no difference between default and empty access
>> privileges with \dp
>
> Yeah.  It's been like that since forever, and nobody's complained
> before, possibly because revoking all privileges for everybody isn't
> a particularly useful real-world case.
>
> One possibility is to start showing "default" when the ACL is null,
> which would be quite easy to implement:
>
>        COALESCE(array_to_string(c.relacl, E'\n'), 'default')
>
> But that might be too big a change.

I don't think that's too big a change.  ISTM we ought to change
something.  Another idea would be to always show the permissions, even
if nothing has been changed from the defaults.

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

In response to

Responses

pgsql-bugs by date

Next:From: Robert HaasDate: 2011-05-15 20:02:10
Subject: Re: Plperl trigger variables no longer global
Previous:From: KOIZUMI SatoruDate: 2011-05-15 13:23:49
Subject: BUG #6026: redundant sentences?

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