pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@surnet.cl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [ADMIN] Permissions not removed when group dropped
Date: Sun, 15 May 2005 17:42:53 -0400
Message-ID: <20050515214253.GA8391@surnet.cl> (raw)
In-Reply-To: <3868.1116084743@sss.pgh.pa.us>
References: <E2F600719FA6FF438A680A22A00DA43C05F7AA2C@EXCHANGEDS01.ds.ad.adp.com>
	<20050513213505.GB17830@surnet.cl>
	<172.1116038893@sss.pgh.pa.us>
	<20050514053053.GA26186@surnet.cl>
	<3868.1116084743@sss.pgh.pa.us>

[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 CASCADE mode, drop any owned objects within the current database;
> if RESTRICT mode, reject if there are owned objects within the current
> database.
> 
> 4. Auto-drop any remaining references (ACLs and group memberships).
> 
> 5. Drop the user itself.

Sounds reasonable.

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.


> The main problem I see with this is that if you do have a user you want
> to get rid of who owns objects in multiple databases, it's still mighty
> hard to do it.  It'd be nice to have some kind of command that either
> drops or reassigns ownership of everything the user has in the current
> database.  Then you could use that repeatedly until you'd reached a
> point where DROP USER would work.

Hmm.  We could implement something like "DROP USER LOCALLY [CASCADE |
RESTRICT]", which would be a very misleading name for operations 2-4
above.  Additionally, if the user doesn't have references in other
databases, drop the user itself.  (Note it's inconsistent.)

For DROP TABLESPACE, I think we should also provide some sort of DROP
LOCALLY, that drops all objects in the current database.  (Suggestions
for the exact spelling of the option are welcome.)

-- 
Alvaro Herrera (<alvherre[a]surnet.cl>)
"La gente vulgar solo piensa en pasar el tiempo;
el que tiene talento, en aprovecharlo"



view thread (8+ messages)  latest in thread

Message-ID: <20050515214253.GA8391@surnet.cl>
Permalink:  ../20050515214253.GA8391@surnet.cl/
Also on:    postgresql.org/message-id/20050515214253.GA8391@surnet.cl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: alvherre@surnet.cl, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: [ADMIN] Permissions not removed when group dropped
  In-Reply-To: <20050515214253.GA8391@surnet.cl>
  References: <E2F600719FA6FF438A680A22A00DA43C05F7AA2C@EXCHANGEDS01.ds.ad.adp.com> <20050513213505.GB17830@surnet.cl> <172.1116038893@sss.pgh.pa.us> <20050514053053.GA26186@surnet.cl> <3868.1116084743@sss.pgh.pa.us> <20050515214253.GA8391@surnet.cl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox