Re: [HACKERS] [ADMIN] Permissions not removed when group dropped

2005-05-15 Thread Alvaro Herrera
[Moved to -hackers] On Sat, May 14, 2005 at 11:32:23AM -0400, Tom Lane wrote: So what we've got [for DROP USER] is: 1. Reject if any references to user from within other databases (implementation restriction). 2. Reject if user owns any databases or tablespaces (safety feature). 3. If

Re: [HACKERS] [ADMIN] Permissions not removed when group dropped

2005-05-15 Thread Tom Lane
Alvaro Herrera [EMAIL PROTECTED] writes: Additionally we need to think what should happen if the user is the grantor of some privilege. I think we should warn in RESTRICT mode, and in CASCADE, revoke the privilege from the grantee. You mean fail in RESTRICT mode, no? Hmm. We could

Re: [HACKERS] [ADMIN] Permissions not removed when group dropped

2005-05-15 Thread Alvaro Herrera
On Sun, May 15, 2005 at 05:48:56PM -0400, Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: Additionally we need to think what should happen if the user is the grantor of some privilege. I think we should warn in RESTRICT mode, and in CASCADE, revoke the privilege from the grantee.