Re: Coping with huge deferred-trigger lists

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Coping with huge deferred-trigger lists
Date: 2001-05-14 15:06:30
Message-ID: 200105141506.LAA02069@jupiter.jw.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Jan Wieck <JanWieck(at)Yahoo(dot)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?

AFAIK nothing other than the Oid. And that's IMHO a weak one.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2001-05-14 15:07:14 is't late to submit patch for 7.1.2 release ?
Previous Message Gilles DAROLD 2001-05-14 15:03:18 Re: Re: 7.2 items