Re: [PL/PGSQL] (Bug/Feature problem) with recursive Trigger - Mailing list pgsql-general

From Tom Lane
Subject Re: [PL/PGSQL] (Bug/Feature problem) with recursive Trigger
Date
Msg-id 10311.1148761018@sss.pgh.pa.us
Whole thread Raw
In response to [PL/PGSQL] (Bug/Feature problem) with recursive Trigger  ("Froggy / Froggy Corp." <froggy@froggycorp.com>)
List pgsql-general
"Froggy / Froggy Corp." <froggy@froggycorp.com> writes:
> PG7 dont make recursiv, it wait for the end of the trigger BEFORE_UPDATE
> to call the new UPDATE stat and forgot the 3rd AFTER_UPDATE. PG8 is
> better, it call trigger like real recursiv fonction, but allways dismiss
> the 3rd AFTER UPDATE.

There isn't any third AFTER UPDATE because the updates fired by the
trigger override the pending update, and so when the trigger returns
the pending update is abandoned.

This is a really badly designed trigger anyway: why don't you just
modify the NEW row, instead of incurring orders of magnitude more work
by launching an entire new SQL command?

            regards, tom lane

pgsql-general by date:

Previous
From: Richard Smith
Date:
Subject: Per session variables
Next
From: "Froggy / Froggy Corp."
Date:
Subject: Re: [PL/PGSQL] (Bug/Feature problem) with recursive Trigger