Re: tg_trigtuple/tg_newtuple settings in AFTER triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: tg_trigtuple/tg_newtuple settings in AFTER triggers
Date: 2006-08-03 16:05:23
Message-ID: 19984.1154621123@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Michael Fuhr <mike(at)fuhr(dot)org> 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, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zoltan Boszormenyi 2006-08-03 16:06:01 Re: GENERATED ... AS IDENTITY, Was: Re: Feature Freeze
Previous Message Chris Browne 2006-08-03 16:04:17 Re: 8.2 feature set

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Hammond 2006-08-03 16:11:38 Re: Replication Documentation
Previous Message Michael Glaesemann 2006-08-03 15:56:20 Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]