Hmm ... I wonder how hard it would be to teach EXPLAIN ANALYZE to show the runtime expended in each trigger when the statement is of a kind that has triggers. We couldn't break down the time *within* the triggers, but even this info would help a lot in terms of finger pointing ...
Seq Scan on ... (nn.nnn ms) Trigger foo: nn.mmm ms Trigger bar: nn.mmm ms Total time: nn.mmm ms
That would be really cool...
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
