Role membership and DROP - Mailing list pgsql-hackers

From Laurenz Albe
Subject Role membership and DROP
Date
Msg-id 504497aca66bf34bdcdd90bd0bcebdc3a33f577b.camel@cybertec.at
Whole thread Raw
Responses Re: Role membership and DROP  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Building infrastructure for B-Tree deduplication that recognizeswhen opclass equality is also equivalence
Next
From: Alvaro Herrera
Date:
Subject: Re: Creating foreign key on partitioned table is too slow