Re: [HACKERS] [PATCHES] tg_trigtuple/tg_newtuple settings in AFTER triggers

2006-08-03 Thread Tom Lane
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

Re: [HACKERS] [PATCHES] tg_trigtuple/tg_newtuple settings in AFTER triggers

2006-08-03 Thread Michael Fuhr
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

Re: [HACKERS] [PATCHES] tg_trigtuple/tg_newtuple settings in AFTER triggers

2006-08-03 Thread Tom Lane
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,