From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mark Lewis <mark.lewis@mir3.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Delete query takes exorbitant amount of time
Date: Fri, 25 Mar 2005 11:38:37 +0800
Message-ID: <424387BD.3070909@familyhealth.com.au> (raw)
In-Reply-To: <4009.1111717976@sss.pgh.pa.us>
References: <1111709457.9085.127.camel@k2.cet.nau.edu>
<2630.1111711927@sss.pgh.pa.us>
<1111713798.23412.3.camel@amateljan.mirlogic.com>
<4009.1111717976@sss.pgh.pa.us>
> 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...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: chriskl@familyhealth.com.au, tgl@sss.pgh.pa.us, mark.lewis@mir3.com
Subject: Re: Delete query takes exorbitant amount of time
In-Reply-To: <424387BD.3070909@familyhealth.com.au>
References: <1111709457.9085.127.camel@k2.cet.nau.edu> <2630.1111711927@sss.pgh.pa.us> <1111713798.23412.3.camel@amateljan.mirlogic.com> <4009.1111717976@sss.pgh.pa.us> <424387BD.3070909@familyhealth.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox