Re: New default role- 'pg_read_all_data'
От | Georgios Kokolatos |
---|---|
Тема | Re: New default role- 'pg_read_all_data' |
Дата | |
Msg-id | 159861699631.18329.14711450552365728705.pgcf@coridan.postgresql.org обсуждение исходный текст |
Ответ на | Re: New default role- 'pg_read_all_data' (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: New default role- 'pg_read_all_data'
|
Список | pgsql-hackers |
Thank you for the patch. My high level review comment: The patch seems to be implementing a useful and requested feature. The patch applies cleanly and passes the basic regress tests. Also the commitfest bot is happy. A first pass at the code, has not revealed any worthwhile comments. Please allow me for a second and more thorough pass. The commitfest has hardly started after all. Also allow me a series of genuine questions: What would the behaviour be with REVOKE? In a sequence similar to: GRANT ALL ON ... REVOKE pg_read_all_data FROM ... What privileges would the user be left with? Would it be possible to end up in the same privilege only with a GRANT command? Does the above scenario even make sense? Regards,
В списке pgsql-hackers по дате отправления: