Re: Coping with huge deferred-trigger lists - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Coping with huge deferred-trigger lists
Date
Msg-id 9222.989851524@sss.pgh.pa.us
Whole thread Raw
In response to Re: Coping with huge deferred-trigger lists  (Jan Wieck <JanWieck@Yahoo.com>)
Responses Re: Coping with huge deferred-trigger lists  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Jan Wieck <JanWieck@Yahoo.com> writes:
>     The  detail  I'm wondering about most is how you'd know in an
>     UPDATE case which two tuples (one deleted  during  this  XACT
>     and  one inserted) are the two for OLD and NEW in the call to
>     the trigger.

Ugh ... good point.  There's no back-link from the updated tuple to
its original on disk, is there?

Back to the drawing board ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: 7.2 items
Next
From: Oleg Bartunov
Date:
Subject: is't late to submit patch for 7.1.2 release ?