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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, gszpetkowski(at)gmail(dot)com
Cc: 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-26 22:27:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
I wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> 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.

> 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.

Given the complete lack of responses, it's apparent that not too many
people care about this issue.  So I've stuck it on the TODO list;
it doesn't seem like something we should change post-beta1.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Craig RingerDate: 2011-05-26 23:47:08
Subject: Re: BUG #6015: to_hex and negative integer
Previous:From: Emanuel CalvoDate: 2011-05-26 17:38:34
Subject: Re: BUG #6041: Unlogged table was created bad in slave node

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