Your patch has been added to the PostgreSQL unapplied patches list at:
http://momjian.postgresql.org/cgi-bin/pgpatches
It will be applied as soon as one of the PostgreSQL committers reviews
and approves it.
---
Ed
On Wednesday April 4 2007 5:37 pm, Bruce Momjian wrote:
> > Perhaps this could be added to the TODO list? I won't get
> > to it anytime soon.
>
> Yes. What should the TODO text be?
See if the attached patch is acceptable. If not, perhaps the
TODO text should be:
Enable end user to identify de
Ed L. wrote:
> On Wednesday April 4 2007 5:02 pm, Alvaro Herrera wrote:
> > > I guess if the bug were fixed, it'd be a non-issue.
> >
> > Sure, please submit a patch. ?It should not be too difficult.
>
> Perhaps this could be added to the TODO list? I won't get to it
> anytime soon.
Yes. What
On Wednesday April 4 2007 5:02 pm, Alvaro Herrera wrote:
> > I guess if the bug were fixed, it'd be a non-issue.
>
> Sure, please submit a patch. It should not be too difficult.
Perhaps this could be added to the TODO list? I won't get to it
anytime soon.
Ed
---(end o
Ed L. wrote:
> On Wednesday April 4 2007 4:48 pm, Alvaro Herrera wrote:
> > > Yes, but how do identify what they are so that I know if I
> > > want to DROP OWNED them?
> >
> > There's no way AFAICT, short of peeking the catalogs (or
> > information_schema). Try pg_shdepend.
>
> I guess if the bug
On Wednesday April 4 2007 4:48 pm, Alvaro Herrera wrote:
> > Yes, but how do identify what they are so that I know if I
> > want to DROP OWNED them?
>
> There's no way AFAICT, short of peeking the catalogs (or
> information_schema). Try pg_shdepend.
I guess if the bug were fixed, it'd be a non-is
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 different
copy. Thank you.
- Original Message -
From: "Ed L." <[EMAIL PROTECTED]>
To: "Alvaro Herrera" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, April 04, 2007 6:41 PM
Subject: Re: [GENERAL] dropping role w/dependent objects
On Wednesday April 4 2007 4:39 pm, Ed
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 h
On Wednesday April 4 2007 4:41 pm, 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
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;
>
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
Ed L. wrote:
> This is pgsql 8.2.3:
>
> % psql -c "drop role mygroup"
> ERROR: role "mygroup" cannot be dropped because some objects
> depend on it
> DETAIL: 227 objects in this database
>
> How do I identify what these dependent objects are?
Hum, this seems to be a bug. The objects are supp
This is pgsql 8.2.3:
% psql -c "drop role mygroup"
ERROR: role "mygroup" cannot be dropped because some objects
depend on it
DETAIL: 227 objects in this database
How do I identify what these dependent objects are?
I've removed all of the users from this group, turned up server
logging to deb
14 matches
Mail list logo
