Re: Command Triggers

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:22:37
Message-ID: 201201132322.38161.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, December 19, 2011 07:37:46 PM Robert Haas wrote:
> 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.
I personally think this is an error and those details should at least be
available on the c level (e.g. some pg_command_trigger_get_plan() function,
only available via C) to allow sensible playing around with that knowledge. I
don't really see making progress towards a nice interface unless we get
something to play around with out there.

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2012-01-13 22:37:22 Re: Disabled features on Hot Standby
Previous Message Dimitri Fontaine 2012-01-13 22:17:03 Re: Command Triggers