| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Role membership and DROP |
| Date: | 2019-11-13 21:36:11 |
| Message-ID: | 504497aca66bf34bdcdd90bd0bcebdc3a33f577b.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-11-13 22:17:06 | Re: Role membership and DROP |
| Previous Message | Bruce Momjian | 2019-11-13 03:04:59 | Re: Does 'instead of delete' trigger support modification of OLD |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-11-13 21:45:44 | Re: Creating foreign key on partitioned table is too slow |
| Previous Message | Peter Geoghegan | 2019-11-13 21:25:27 | Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence |