Re: BUG #6021: There is no difference between default and empty access privileges with \dp - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6021: There is no difference between default and empty access privileges with \dp
Date
Msg-id 19543.1306276131@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #6021: There is no difference between default and empty access privileges with \dp  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: BUG #6021: There is no difference between default and empty access privileges with \dp
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> On Sun, May 15, 2011 at 5:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Robert Haas <robertmhaas@gmail.com> writes:
>>> On Thu, May 12, 2011 at 6:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> 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.

>> That would require psql to have local knowledge about what the defaults
>> are, which is someplace I'd rather not go ...

> Ugh.  It's too bad the server doesn't expose that.  But given that it
> doesn't, your idea sounds good to me.

So is this something we should slip into 9.1, or is it 9.2 material?
I've got no strong opinion about that myself.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "manish singh"
Date:
Subject: BUG #6037: error on restarting slave - cp: cannot stat `pg_xlog....`: no such file or ...
Next
From: nikolairoman
Date:
Subject: Re: BUG #5807: psql fails to launch with "Cannot read termcap database; using dumb terminal settings. Aborted"