Re: Why are triggers semi-deferred?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why are triggers semi-deferred?
Date: 2003-05-05 16:55:47
Message-ID: 28668.1052153747@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> But in the case of multi-row updates, won't it be expensive to keep all the
> context?

We do that already for AFTER triggers. The question is just when the
trigger ought to be fired.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-05-05 16:58:04 Re: Why are triggers semi-deferred?
Previous Message Tom Lane 2003-05-05 16:54:00 Re: Transform groups (more FE/BE protocol issues)