Re: BUG #6421: Revoke column level privilage

Поиск
Список
Период
Сортировка
От bdmytrak@eranet.pl
Тема Re: BUG #6421: Revoke column level privilage
Дата
Msg-id 8564163.114.1328132994056.JavaMail.omnix03@wlas3
обсуждение исходный текст
Ответ на BUG #6421: Revoke column level privilage  (bdmytrak@eranet.pl)
Список pgsql-bugs
Thanks for Your answer.
Works as designed - I have to get used.
Please notice the return message from REVOKE ALL command:
myDatabase=# REVOKE ALL("Column1") ON public."tblTest" FROM public;
REVOKE
myDatabase=# \dp public."tblTest"
Access privileges
Schema | Name | Type | Access privileges | Column access
privileges
--------+---------+-------+----------------------------+--------------------------
public | tblTest | table | postgres=arwdDxt/postgres +| Column1:
+
| | | otherUser=ar*wdxt/postgres | =r/otherUser
(1 row)
return message is REVOKE, but privileges are not really revoked ? there should be at least warning message generated.
REVOKE...CASCADEworks fine. 
AFAIK SQL Standard defines GRANTED BY. I haven't found it in PosgtreSQL documentation, so assume it is not implemented.
Ithink it is good idea to imlement it, this could help in that case. 
Regards,
Bartek
--- Oryginalna wiadomo?? ---
Od: Tom Lane [mailto: tgl@sss.pgh.pa.us]
Wys?ane: Tuesday, January 31, 2012 03:03 AM
Do: bdmytrak@eranet.pl
Kopia: pgsql-bugs@postgresql.org
Temat: Re: [BUGS] BUG #6421: Revoke column level privilage
bdmytrak@eranet.pl writes:
> Cannot revoke column level privilages.
AFAICS this is not a bug, and it's certainly not specific to
column-level privileges. You had "postgres" grant some privileges to
"otherUser" with grant option, and then had "otherUser" re-grant those
privileges to public. "postgres" cannot revoke the re-grant directly.
You can have it revoke "otherUser"'s grant option. (I think this will
require the CASCADE keyword if there are dependent privileges that
have to be revoked in consequence.) Or you can log in as "otherUser"
and revoke the privilege grants made by that role. This is per design
and AFAIK it's per the SQL standard's requirements.
There's a lot of fine print in the Notes sections of the GRANT and
REVOKE reference pages, which you might find helpful.
regards, tom lane

Pozdrawiam,
Bartek

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #6426: Complex query runs 10 times longer with "LIMIT 20"
Следующее
От: keith@omniti.com
Дата:
Сообщение: BUG #6428: pg_restore -l not consistent with function comments