From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Subject: | tg_trigtuple/tg_newtuple settings in AFTER triggers |
Date: | 2006-08-02 02:24:03 |
Message-ID: | 20060802022403.GA1289@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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 stylistically flawed then please advise
and I'll rework it. Thanks.
--
Michael Fuhr
Attachment | Content-Type | Size |
---|---|---|
trigger.c.diff | text/plain | 2.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-08-02 02:27:25 | Re: [PATCHES] Replication Documentation |
Previous Message | Joe Conway | 2006-08-02 02:10:50 | Re: Values list-of-targetlists patch for comments (was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-08-02 02:27:25 | Re: [PATCHES] Replication Documentation |
Previous Message | Joe Conway | 2006-08-02 02:10:50 | Re: Values list-of-targetlists patch for comments (was Re: |