Search Postgresql Archives

plperl function called > once in cascading triggers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux