From: Tom Lane Date: Wed, 2 Mar 2011 16:17:03 +0000 (-0500) Subject: Correct mistaken claims about EXPLAIN ANALYZE's handling of triggers. X-Git-Tag: REL9_1_ALPHA4~75 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7e49330cad885a76441253da74b88e7d2f27c9f0;p=postgresql Correct mistaken claims about EXPLAIN ANALYZE's handling of triggers. Time spent executing AFTER triggers is not included in the runtime of the associated ModifyTable node; in my patch of yesterday I confused queuing of these triggers with their actual execution. Spotted by Marko Tiikkaja. --- diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index 72baad27f1..9d5b709aec 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -436,10 +436,13 @@ WHERE t1.unique1 < 100 AND t1.unique2 = t2.unique2; applying the table changes is charged to a top-level Insert, Update, or Delete plan node. (The plan nodes underneath this node represent the work of locating the old rows and/or computing the new ones.) - Time spent firing triggers, if any, is charged to the Insert, - Update, or Delete node, and is also shown separately for each trigger. - Note, however, that deferred triggers will not be fired until end of - transaction and are thus not accounted for in the output of + Time spent executing BEFORE triggers, if any, is charged to + the related Insert, Update, or Delete node, although time spent executing + AFTER triggers is not. The time spent in each trigger + (either BEFORE or AFTER) is also shown separately + and is included in total runtime. + Note, however, that deferred constraint triggers will not be executed + until end of transaction and are thus not shown by EXPLAIN ANALYZE.