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

Tom Lane,

	  er, your explanation is reasonable.

	  But at least the comment
	  if (newtuple !=3D tuple) /* modified by Trigger(s) */
	  {
		.....
	  is likely to misdirect us.

	  It took me a few hours to figure it out. :-(

=3D=3D=3D=3D=3D=3D=3D 2008-06-10 23:43:00 In your letter you
say:=3D=3D=3D=
=3D=3D=3D=3D

>"billy" <billywq@[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@[EMAIL PROTECTED]
)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-hackers

=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1billy
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1billywq@[EMAIL PROTECTED]
 via pgsql-hackers mailing list (pgsql-hackers@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers