Postgres Pro
Downloads
Home   >   mailing lists

Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable - Mailing list pgsql-hackers

From Tom Lane
Subject Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable
Date
Msg-id 29052.1213155783@sss.pgh.pa.us
Whole thread Raw
In response to why copy tuple in the end of trigger when nothing changed in NEW OLD record variable  ("billy" <billywq@163.com>)
List pgsql-hackers
Tree view 
"billy" <billywq@163.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

pgsql-hackers by date:

Previous
From: "billy"
Date:
Subject: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable
Next
From: "billy"
Date:
Subject: Re: why copy tuple in the end of trigger when nothing changed in NEW OLD record variable