Re: schema access privs

Поиск
Список
Период
Сортировка
От Ray Stell
Тема Re: schema access privs
Дата
Msg-id 20110405152649.GC19943@cns.vt.edu
обсуждение исходный текст
Ответ на Re: schema access privs  (Vibhor Kumar <vibhor.kumar@enterprisedb.com>)
Список 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.

В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Why security-definer functions are executable by public by default?
Следующее
От: Ben Chobot
Дата:
Сообщение: Re: Named advisory locks