| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Greg Smith <greg(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: Command Triggers |
| Date: | 2012-01-14 21:46:18 |
| Message-ID: | m2ipkeq7o5.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> But on the flip side, I think we're generally a bit more flexible
> about exposing things via C than through the procedural languages.
So we could still expose the parsetree of the current command. I wonder
if it's already possible to get that from a C coded trigger, but I'll
admit I'm yet to code a trigger in C. Will look into that.
Then as Andres proposed, a new function would be available to get the
value, we're not changing the trigger procedure function API in case the
language is C…
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-01-14 21:53:18 | lots of unused variable warnings in assert-free builds |
| Previous Message | Pavel Stehule | 2012-01-14 20:31:54 | Re: JSON for PG 9.2 |