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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-05-15 20:02:10 | Re: Plperl trigger variables no longer global |
Previous Message | KOIZUMI Satoru | 2011-05-15 13:23:49 | BUG #6026: redundant sentences? |