Re: Command Triggers

Dimitri Fontaine <dimitri@2ndquadrant.fr>

From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Greg Smith <greg@2ndquadrant.com>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, Bruce Momjian <bruce@momjian.us>, Alvaro Herrera <alvherre@commandprompt.com>

Date: 2012-01-13T22:17:03Z

Lists: pgsql-hackers

Attachments

command-trigger.v5.patch.gz (application/octet-stream) patch v5

Robert Haas <robertmhaas@gmail.com> writes:
> Maybe we should try to split the baby here and defer the question of
> whether to expose any of the parse tree internals, and if so how much,
> to a future release.  It seems to me that we could design a fairly
> useful set of functionality around AFTER-CREATE, BEFORE-DROP, and
> maybe even AFTER-ALTER triggers without exposing any parse tree
> details.

Please find attached v5 of the patch, with nodeToString() support removed.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support