> The effects don't stop propagating there, either. The decision > not to insert the tuple must be reported up still further, so > that the executor knows not to run any AFTER INSERT/UPDATE > triggers and knows not to count the tuple as inserted/updated > for the command completion report.
But what about BEFORE insert/update triggers which could insert records too? Vadim ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
