Skip site navigation (1) Skip section navigation (2)


From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: LIST OWNED BY...
Date: 2012-02-29 18:27:43
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Feb 29, 2012 at 12:20 PM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 29 February 2012 17:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Thom Brown <thom(at)linux(dot)com> writes:
>>> So could we introduce either a command to show which objects are owned
>>> by a particular role, or allow a dry-run of DROP OWNED BY?
>> It's always been possible to do that:
>>        begin;
>>        drop owned by joe;
>>        rollback;
>> I believe this is already the recommended approach if you're concerned
>> about what DROP CASCADE will do.
> No, the cascade part is fine.  It's the objects which won't cause a
> cascade that are an issue.  Putting it in a transaction for rolling
> back doesn't help find out what it intends to drop.
> How can the user tell what the statement would drop (ignoring cascades)?

It's certainly possible to write a query for this, but I think this
gets back to the old argument about whether every client (and every
end-user) should be required to reimplement this, or whether maybe we
ought to provide some server functionality around it.

Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2012-02-29 18:32:48
Subject: Re: controlling the location of server-side SSL files
Previous:From: Thom BrownDate: 2012-02-29 18:23:29
Subject: Re: LIST OWNED BY...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group