From: Mark Lewis <mark.lewis@mir3.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Delete query takes exorbitant amount of time
Date: Mon, 28 Mar 2005 09:35:50 -0800
Message-ID: <1112031350.23412.131.camel@amateljan.mirlogic.com> (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>
Tom Lane Wrote:
> 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
So I got the latest from CVS on Friday night to see how hard it would be
to implement this, but it turns out that Tom has already committed the
improvement, so I'm in Tom's fan club today. I imported my test dataset
and was almost immediately able to track down the cause of my
performance problem.
Thanks!
Mark Lewis
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mark.lewis@mir3.com, tgl@sss.pgh.pa.us
Subject: Re: Delete query takes exorbitant amount of time
In-Reply-To: <1112031350.23412.131.camel@amateljan.mirlogic.com>
* 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