From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Possible patch to remove "triggered data change" support |
Date: | 2001-11-13 01:37:46 |
Message-ID: | 29709.1005615466@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-11-13 01:51:16 | Re: Patch to add Heimdal kerberos support |
Previous Message | Tom Lane | 2001-11-13 01:32:51 | Re: ALTER TABLE RENAME fix |