| From: | Vibhor Kumar <vibhor(dot)kumar(at)enterprisedb(dot)com> |
|---|---|
| To: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
| Cc: | "pgsql-general(at)postgresql(dot)org List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: schema access privs |
| Date: | 2011-04-05 13:03:46 |
| Message-ID: | A89DCF47-4E13-4CAC-9281-7B036B0BEB70@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Apr 5, 2011, at 6:07 PM, Ray Stell wrote:
> On Tue, Apr 05, 2011 at 03:58:46PM +0530, Vibhor Kumar wrote:
>>
>> Following are details:
>> postgres=UC/postgres+
>> [user] [privs] /[ ROLE who granted privs.
>
> What's the logic for reporting the U priv twice?
If you are talking about following:
=U/postgres
[public]=[access][ ROLE who granted privs]
for public there will no username, its always =(equals to) followed by access/[Role who granted privs].
Thanks & Regards,
Vibhor Kumar
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
vibhor(dot)kumar(at)enterprisedb(dot)com
Blog:http://vibhork.blogspot.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-04-05 13:11:41 | Re: Named advisory locks |
| Previous Message | Ray Stell | 2011-04-05 12:37:25 | Re: schema access privs |