On Sun, May 15, 2011 at 5:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, May 12, 2011 at 6:20 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
The Enterprise PostgreSQL Company
In response to
pgsql-bugs by date
|Next:||From: Robert Haas||Date: 2011-05-23 17:12:40|
|Subject: Re: BUG #5984: Got FailedAssertion("!(opaque->btpo_prev ==
target)", File: "nbtpage.c", Line: 1166)|
|Previous:||From: Tom Lane||Date: 2011-05-23 16:54:26|
|Subject: Re: BUG #6035: server crash when executing recursive query (trying to allocate 16 Exabyte memory) |