plperl function called > once in cascading triggers - Mailing list pgsql-general

From Kenneth Downs
Subject plperl function called > once in cascading triggers
Date
Msg-id 45F88EB4.3000109@secdat.com
Whole thread Raw
Responses Re: plperl function called > once in cascading triggers  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
Consider the case where an AFTER STATEMENT trigger calls a plperl
function which performs a loop.  Inside of the loop it updates at least
one other table.

The table being updated has an AFTER STATEMENT trigger that calls the
same plperl function (w/different parms of course), which goes into
another loop.

Presumably this could go to any number of levels.

What I have noticed is that once the innermost instance exits, none of
the outer instances execute any further, suggesting that the plperl
routine is not "re-entrant" (if I am using that term correctly).

Is this right?  Am I missing something?


pgsql-general by date:

Previous
From: Ken Johanson
Date:
Subject: Native type for storing fractions (e.g 1/3)?
Next
From: Tom Lane
Date:
Subject: Re: How to write a function that manipulates a set of results