Re: Command Triggers

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Greg Smith <greg(at)2ndquadrant(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: Command Triggers
Date: 2012-01-13 22:17:03
Message-ID: m2r4z3tfhc.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)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

Attachment Content-Type Size
command-trigger.v5.patch.gz application/octet-stream 32.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-01-13 22:22:37 Re: Command Triggers
Previous Message Josh Berkus 2012-01-13 22:16:04 Re: 9.3 feature proposal: vacuumdb -j #