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: Mon, 16 May 2005 00:04:31 -0400
Message-ID: <20050516040431.GA9147@surnet.cl> (raw)
In-Reply-To: <3358.1116193736@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>
	<20050515214253.GA8391@surnet.cl>
	<3358.1116193736@sss.pgh.pa.us>

On Sun, May 15, 2005 at 05:48:56PM -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@surnet.cl> 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?

Yes, with a message indicating what happened.

> > 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.)
> 
> I'd go for something more like "DROP OWNED OBJECTS", which'd be just
> the stuff internal to the current database (owned objects and ACL
> entries).  You don't need to drop group memberships per-database.

Ok.

-- 
Alvaro Herrera (<alvherre[a]surnet.cl>)
"Find a bug in a program, and fix it, and the program will work today.
Show the program how to find and fix a bug, and the program
will work forever" (Oliver Silfridge)



view thread (8+ messages)

Message-ID: <20050516040431.GA9147@surnet.cl>
Permalink:  ../20050516040431.GA9147@surnet.cl/
Also on:    postgresql.org/message-id/20050516040431.GA9147@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: <20050516040431.GA9147@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> <3358.1116193736@sss.pgh.pa.us> <20050516040431.GA9147@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