From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thom Brown <thom(at)linux(dot)com>, 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-03-13 18:56:46 |
Message-ID: | 20120313185646.GC23967@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 29, 2012 at 01:27:43PM -0500, Robert Haas wrote:
> 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.
Is this a TODO?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2012-03-13 19:02:18 | Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation) |
Previous Message | Bruce Momjian | 2012-03-13 18:53:26 | Re: pg_upgrade and statistics |