Re: Reducing the memory footprint of large sets of pending triggers

On Sat, 2008-10-25 at 08:48 -0400, Tom Lane wrote:
> 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
> > category.
>
> They're hardly "duplicates": each event is for a different tuple.

That's what makes it hard; we may find the same trigger parameter values
but on different tuples.

> 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.

Me neither, yet.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support