| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Hans-Juergen Schoenig <postgres(at)cybertec(dot)at> |
| Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP ROLE dependency tracking ... |
| Date: | 2008-05-25 14:01:08 |
| Message-ID: | 20080525140108.GD24891@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hans-Juergen Schoenig wrote:
> when thinking of REASSIGNED OWNED people tend to think about tables
> rather than about CONNECT rights.
> i would suggest to make DROP ROLE just kill the role unless there is a
> real object depending on it.
> i would not see a permission to be an object. what do you think?
Yes, this might make some sense. (Keep in mind that db CONNECT
privileges were invented after REASSIGN OWNED). Perhaps we could make
exceptions -- in which case it would be good to investigate which
exceptions we need (i.e. for all object types that we support, which
ones we should be caring about and which ones we should ignore).
I'm stuck in Canuckistan for a week still, so I expect your detailed
proposal by when I get back home ;-)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-05-25 14:05:10 | Re: \df displaying volatility |
| Previous Message | Hans-Juergen Schoenig | 2008-05-25 13:32:32 | Re: DROP ROLE dependency tracking ... |