Michael Fuhr <[EMAIL PROTECTED]> writes:
> Thanks. Alvaro made the following suggestion but didn't copy the
> list -- shall I do what he suggested and submit the changes as
> another patch?
> Alvaro Herrera wrote:
>> I'd add an Assert() on the second hunk to make sure newtuple is only set
>> in U
On Thu, Aug 03, 2006 at 12:05:23PM -0400, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Set tg_trigtuple/tg_newtuple in AFTER triggers according to whether
> > old and new tuples were supplied rather than blindly setting them
> > according to the event type. Per discussion in pgsq
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Set tg_trigtuple/tg_newtuple in AFTER triggers according to whether
> old and new tuples were supplied rather than blindly setting them
> according to the event type. Per discussion in pgsql-hackers.
Looks good, applied.
regards,
Set tg_trigtuple/tg_newtuple in AFTER triggers according to whether
old and new tuples were supplied rather than blindly setting them
according to the event type. Per discussion in pgsql-hackers.
http://archives.postgresql.org/pgsql-hackers/2006-07/msg01601.php
If the patch is logically or styli
