Re: schema access privs

From: Ray Stell <stellr(at)cns(dot)vt(dot)edu>
To: Vibhor Kumar <vibhor(dot)kumar(at)enterprisedb(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: schema access privs
Date: 2011-04-05 15:26:49
Message-ID: 20110405152649.GC19943@cns.vt.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 05, 2011 at 06:33:46PM +0530, Vibhor Kumar wrote:
>
> 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?
>
> [public]=[access][ ROLE who granted privs]
>
> for public there will no username, its always =(equals to) followed by access/[Role who granted privs].

template1=# \pset expanded
Expanded display is on.
template1=# \dn+ information_schema
List of schemas
-[ RECORD 1 ]-----+---------------------
Name | information_schema
Owner | postgres
Access privileges | postgres=UC/postgres
| =U/postgres
Description |

>From this:

template1=# \pset expanded
Expanded display is off.
template1=# \dn+ information_schema
List of schemas
Name | Owner | Access privileges | Description
--------------------+----------+----------------------+-------------
information_schema | postgres | postgres=UC/postgres+|
| | =U/postgres |
(1 row)

I was reading 3 fields:

1. postgres=UC
2. postgres=U
3. postgres

which made no sense at all.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ben Chobot 2011-04-05 15:29:25 Re: Named advisory locks
Previous Message Zeev Ben-Sender 2011-04-05 15:22:16 Is index rebuilt upon updating table with the same values as already existing in the table?