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

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

From: Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-13 01:33:54
Message-ID: BANLkTikA5vdtOrwBPZbmpuwd1to8JmMt9Q@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
2011/5/13 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Grzegorz Szpetkowski <gszpetkowski(at)gmail(dot)com> writes:
>> I see that I just confused old PostgreSQL 8.3 curly bracket behaviour
>> with new 8.4/9.0 (I am using 8.3 all the time):
>
> Oh, you're right --- so I was mistaken to claim it had always been like
> that.  Before we started using array_to_string here, you *could* tell
> the difference between default privileges and no privileges.
>
> The precedent of previous versions makes it more plausible that we
> should print '{}' for no privileges, but I'm still not quite convinced.
> Anybody else have an opinion?
>
>                        regards, tom lane
>

I think that in such case it seems to be best solution (if any of
course) to provide "null" if object has no privileges:

"" - default ACL
"miriam=arwdDxt/miriam" - some ACL
"null" - no ACL

Regards,
Grzegorz Spetkowski

In response to

pgsql-bugs by date

Next:From: Alessio PolleroDate: 2011-05-13 16:13:25
Subject: BUG #6025: psql show password inserted in database restore
Previous:From: Tom LaneDate: 2011-05-12 23:57:04
Subject: Re: BUG #6021: There is no difference between default and empty access privileges with \dp

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