Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "billy" <billywq(at)163(dot)com>
Cc: pghacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable
Date: 2008-06-11 03:43:03
Message-ID: 29052.1213155783@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"billy" <billywq(at)163(dot)com> 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message billy 2008-06-11 04:57:15 Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable
Previous Message billy 2008-06-11 03:21:31 why copy tuple in the end of trigger when nothing changed in NEW OLD record variable