Role membership and DROP

Поиск
Список
Период
Сортировка
От Laurenz Albe
Тема Role membership and DROP
Дата
Msg-id 504497aca66bf34bdcdd90bd0bcebdc3a33f577b.camel@cybertec.at
обсуждение исходный текст
Ответы Re: Role membership and DROP  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
I realized only today that if role A is a member of role B,
A can ALTER and DROP objects owned by B.

I don't have a problem with that, but the documentation seems to
suggest otherwise.  For example, for DROP TABLE:

   Only the table owner, the schema owner, and superuser can drop a table.

Should I compose a doc patch, or is that too much of a corner case
to mention?  I wanted to ask before I do the repetetive work.

Yours,
Laurenz Albe




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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Building infrastructure for B-Tree deduplication that recognizeswhen opclass equality is also equivalence
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Creating foreign key on partitioned table is too slow