Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> So please find attached to this email an implementation of the sql_drop
> event trigger, that refrains on exposing any new information to the
Already a v1 of that patch, per comments from Álvaro I reuse the
ObjectAddresses facility rather than building my own List of object
Note that with that in place it's now easy to also add support for the
DROP OWNED BY command, but that's left for a future patch as I expect
some amount of discussion to go about it.
Also, I removed the code that was doing de-deduplication of the object
addresses we collect, now trusting performMultipleDeletions() not to
screw us up. There's a use case that needs particular attention here,
DROP TABLE foo, foo;
I'm not sure we want to deduplicate foo in the pg_dropped_objects()
output in that case, so I've not done so in this version of the patch.
Also, Álvaro is concerned that the cost of deduplicating might be higher
than what we want to take here.
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
In response to
pgsql-hackers by date
|Next:||From: Pavan Deolasee||Date: 2013-01-30 18:07:41|
|Subject: Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples|
|Previous:||From: Simon Riggs||Date: 2013-01-30 17:26:26|
|Subject: Re: pgsql: Fast promote mode skips checkpoint at end of recovery.|