Tom Lane b339d1fff6 Fire non-deferred AFTER triggers immediately upon query completion, ...

rather than when returning to the idle loop.  This makes no particular
difference for interactively-issued queries, but it makes a big difference
for queries issued within functions: trigger execution now occurs before
the calling function is allowed to proceed.  This responds to numerous
complaints about nonintuitive behavior of foreign key checking, such as
http://archives.postgresql.org/pgsql-bugs/2004-09/msg00020.php, and
appears to be required by the SQL99 spec.
Also take the opportunity to simplify the data structures used for the
pending-trigger list, rename them for more clarity, and squeeze out a
bit of space.

2004-09-10 18:40:09 +00:00

..

FAQ

Add index mention:

2004-09-01 03:28:15 +00:00

sgml

Fire non-deferred AFTER triggers immediately upon query completion,

2004-09-10 18:40:09 +00:00

Makefile

$Header: -> $PostgreSQL Changes ...

2003-11-29 19:52:15 +00:00