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

From Robert Haas
Subject Re: BUG #6021: There is no difference between default and empty access privileges with \dp
Date
Msg-id BANLkTi=jjGNev+f-h_j03pd-wUb4DDxaKw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6021: There is no difference between default and empty access privileges with \dp  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #6021: There is no difference between default and empty access privileges with \dp
List pgsql-bugs
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:
>>>
>>> =A0 =A0 =A0 =A0COALESCE(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. =A0ISTM we ought to change
>> something. =A0Another 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.

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #6035: server crash when executing recursive query (trying to allocate 16 Exabyte memory)
Next
From: Robert Haas
Date:
Subject: Re: BUG #5984: Got FailedAssertion("!(opaque->btpo_prev == target)", File: "nbtpage.c", Line: 1166)