From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Luki Rustianto" <lukirus(at)gmail(dot)com> |
Cc: | "General PostgreSQL List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pg7.4.x plpgsql trigger execution order bug |
Date: | 2007-06-28 05:26:05 |
Message-ID: | 20928.1183008365@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Luki Rustianto" <lukirus(at)gmail(dot)com> writes:
> I've found on pg7.4.x that plpgsql trigger will not wait for finishing
> one line of command before executing to the next line, specially if
> that command is firing another trigger on another table. This is very
> wrong on my point of view. This only happen on pg7.
To quote the 8.0 release notes:
: Observe the following incompatibilities:
: ...
: Nondeferred AFTER triggers are now fired immediately after completion of
: the triggering query, rather than upon finishing the current interactive
: command. This makes a difference when the triggering query occurred
: within a function: the trigger is invoked before the function proceeds
: to its next operation.
This change is not going to be back-patched into 7.x, because it would
break applications that depended on the old behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mavinakuli, Prasanna (STSD) | 2007-06-28 05:31:33 | Looking for help regarding getting the latest inserted sequence value. |
Previous Message | Tom Lane | 2007-06-28 05:01:59 | Re: Column Default Clause and User Defined Functions |