git.postgresql.org Git - postgresql.git/commitdiff

git projects / postgresql.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 82a0e35)
Correct mistaken claims about EXPLAIN ANALYZE's handling of triggers.
Wed, 2 Mar 2011 16:17:07 +0000 (11:17 -0500)
Wed, 2 Mar 2011 16:17:07 +0000 (11:17 -0500)
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 1c18274e89b645380b96fe3cc4fac930269f5246..65d602003141e46ebe56c000e02d6d5048355720 100644 (file)
--- 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 <literal>BEFORE</> triggers, if any, is charged to
+ the related Insert, Update, or Delete node, although time spent executing
+ <literal>AFTER</> triggers is not. The time spent in each trigger
+ (either <literal>BEFORE</> or <literal>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
<command>EXPLAIN ANALYZE</command>.
</para>
This is the main PostgreSQL git repository.
RSS Atom

AltStyle によって変換されたページ (->オリジナル) /