Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> A much better objective would be to remove duplicate trigger calls, so
> there isn't any build up of trigger data in the first place. That would
> apply only to immutable functions. RI checks certainly fall into that
They're hardly "duplicates": each event is for a different tuple.
For RI checks, once you get past a certain percentage of the table it'd
be better to throw away all the per-tuple events and do a full-table
verification a la RI_Initial_Check(). I've got no idea about a sane
way to make that happen, though.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-10-25 12:57:43|
|Subject: Impending back branch update releases|
|Previous:||From: Simon Riggs||Date: 2008-10-25 12:36:19|
|Subject: Re: Reducing the memory footprint of large sets ofpending triggers|