Re: tables permissions once again

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: tables permissions once again
Дата
Msg-id 8417.973292173@sss.pgh.pa.us
обсуждение исходный текст
Ответ на tables permissions once again  (Partyka Robert <bobson@saturn.alpha.pl>)
Список pgsql-hackers
Partyka Robert <bobson@saturn.alpha.pl> writes:
> #create table ala(a int4);
> CREATE

> #\z
> Access permissions for database "a"
>  Relation | Access permissions
> ----------+--------------------
>  ala      |
> (1 row)

> #revoke all on ala from public;
> CHANGE
> #\z
> Access permissions for database "a"
>  Relation |  Access permissions
> ----------+-----------------------
>  ala      | {"=","postgres=arwR"}
> (1 row)

> hmmm.... is everything work ok ?

Yup, that's the expected behavior.  Initially the relacl entry for a new
table is NULL, which the system will interpret as default access rights
(namely, world=no rights, owner=all rights).  As soon as you issue a
GRANT or REVOKE, a real ACL gets installed --- which will consist of the
default access rights made explicit and then modified per your GRANT or
REVOKE.  At that point you see something in \z, whereas psql doesn't
show anything in \z for a NULL acl entry.

AFAIK it's always worked like that...
        regards, tom lane


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

Предыдущее
От: Dan Moschuk
Дата:
Сообщение: VACUUM causes violent postmaster death
Следующее
От: Alfred Perlstein
Дата:
Сообщение: Re: VACUUM causes violent postmaster death