Tom Lane,
er, your explanation is reasonable.
But at least the comment
if (newtuple != tuple) /* modified by Trigger(s) */
{
.....
is likely to misdirect us.
It took me a few hours to figure it out. :-(
======= 2008-06-10 23:43:00 In your letter you say:=======
>"billy" <[EMAIL PROTECTED]> writes:
>> I think we can add some judgment conditions in function
>> plpgsql_exec_trigger() to avoid this problem.
>
>I don't especially see the point of adding extra complexity here.
>AFAICS you are talking about avoiding one or two palloc/pfree
>cycles, which is surely down in the noise compared to the cost of
>calling a plpgsql trigger.
>
> regards, tom lane
>
>--
>Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-hackers
billy
[EMAIL PROTECTED]
2008-06-11
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
