From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: dropping role w/dependent objects |
Date: | 2007-04-04 22:57:22 |
Message-ID: | 20070404225722.GI19251@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Ed L. wrote:
> On Wednesday April 4 2007 4:39 pm, Ed L. wrote:
> > On Wednesday April 4 2007 4:35 pm, Alvaro Herrera wrote:
> > > Note that you can give the objects owned by that role to
> > > someone else with REASSIGN OWNED, and drop the objects with
> > > DROP OWNED (note that they act differently regarding grants;
> > > see the docs)
> >
> > Yes, but how do identify what they are so that I know if I
> > want to DROP OWNED them?
>
> The REASSIGN OWNED appears to be insufficient:
>
> % psql -c "reassign owned by mygroup to mydba"
> REASSIGN OWNED
> % psql -c "drop group mygroup"
> ERROR: role "mygroup" cannot be dropped because some objects
> depend on it
> DETAIL: 225 objects in this database
Right. REASSIGN OWNED changes ownership to someone else, but leaves
grants untouched. DROP OWNED revokes the permissions the role might
have. This is the intended behavior.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-04-04 23:02:46 | Re: dropping role w/dependent objects |
Previous Message | Peter Eisentraut | 2007-04-04 22:57:09 | Re: a couple of newbie question - deferrable, varchar vs text, 2 dbs |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-04-04 23:02:46 | Re: dropping role w/dependent objects |
Previous Message | Ed L. | 2007-04-04 22:55:54 | Re: dropping role w/dependent objects |