Re: Possible patch to remove "triggered data change" support - Mailing list pgsql-patches

From Tom Lane
Subject Re: Possible patch to remove "triggered data change" support
Date
Msg-id 29709.1005615466@sss.pgh.pa.us
Whole thread Raw
In response to Possible patch to remove "triggered data change" support  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I assume we still need a queue for deferred triggers, right?

There's still a queue.  But it saves fewer events for shorter intervals
than it used to.  Example: in the present code, if you have *any*
deferred triggers (for INSERT, UPDATE, or DELETE) on a rel then queue
entries are made for *all* triggerable events (INSERT, UPDATE, or
DELETE) on that rel.  In the proposed patch, if you have only an AFTER
INSERT trigger then no queue entries are made for UPDATE or DELETE
events, etc.  This has a direct bearing on the number of queue entries
made in RI scenarios, since the RI triggers are for subsets of events.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible patch to remove "triggered data change" support
Next
From: Tom Lane
Date:
Subject: Re: ALTER TABLE RENAME fix