Re: Making AFTER triggers act properly in PL functions - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: Making AFTER triggers act properly in PL functions
Date
Msg-id 20040907160325.E17044@megazone.bigpanda.com
Whole thread Raw
In response to Re: Making AFTER triggers act properly in PL functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Making AFTER triggers act properly in PL functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 7 Sep 2004, Tom Lane wrote:

> Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> > If I'm reading the above correctly, I think DeferredTriggerSetState may
> > need to change a little if EndQuery works on a separate list of triggers
> > because I believe set constraints immediate currently depends on EndQuery
> > going over the entire list of saved deferred triggers.
>
> But it would.  What I'm imagining is that the current list remains the
> same, but it only contains trigger events from already-completed statements.
> The per-query lists would be "staging areas" for gathering events from
> still-active statements.

I misread then.  I thought that you were proposing that EndQuery look only
at the per-query list and then add the deferred items that weren't fired
to the main list but never go over that list.


pgsql-hackers by date:

Previous
From: Thomas F.O'Connell
Date:
Subject: Re: contrib/start-scripts/linux on Debian
Next
From: Tom Lane
Date:
Subject: Re: Making AFTER triggers act properly in PL functions