Re: fine grained trigger time specification...

On Tue, 23 Mar 2004 10:17:31 -0600
Bruno Wolff III <bruno(at)wolff(dot)to> wrote:

> On Tue, Mar 23, 2004 at 15:19:13 +0100,
> Erik Thiele <erik(at)thiele-hydraulik(dot)de> wrote:
> > now sadly i am getting this kind of problem:
> >
> >
> > zeit=> insert into a select
> > nextval('delmeseq'),personalnumber,datum,datum from calendar where
> > type=10409;
> > INSERT 0 581 <-- see, 581 inserts which is pretty much :)
> > zeit=> commit; <-- now i have to wait for 581 calls of alwayscheck
> >
> >
> > since alwayscheck is not the fastest function on earth, i'd like to have
> > it called on commit time if at least one of table a or b was modified,
> > but always only once per commit. is there a way to formulate this:
> >
> > ARRANGE FOR CALL OF FUNCTION alwayscheck() ON COMMIT WHEN AT LEAST ONE
> > OF TABLE a OR TABLE b WAS MODIFIED BUT CALL THE FUNCTION AT MOST ONE
> > TIME;
>
> Wouldn't changing your triggers to be for each statement instead of for
> each row fix this?

no, because

1) my postgresql version does not support "for each statement"

2) i am also inserting with multiple insert commands thousands of entries.

--
Erik Thiele