pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Oleg Bartunov <oleg@sai.msu.su>
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 08:38:33 +0300 (MSK)
Message-ID: <Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su> (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>

On Thu, 24 Mar 2005, Tom Lane wrote:

> Mark Lewis <mark.lewis@mir3.com> writes:
>> I've got a similar problem with deletes taking a very long time.  I know
>> that there are lots of foreign keys referencing this table, and other
>> foreign keys referencing those tables, etc.  I've been curious, is there
>> a way to find out how long the foreign key checks take for each
>> dependent table?
>
> There is not any easy way at the moment.
>
> 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

and if you add

         Index foo_idx: nn.mm ss
 	Heap  foo_tbl: nn.mm ss


>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>

 	Regards,
 		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83



view thread (60+ messages)  latest in thread

Message-ID: <Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su>
Permalink:  ../Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su/
Also on:    postgresql.org/message-id/Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su

 · 

reply

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: oleg@sai.msu.su, tgl@sss.pgh.pa.us, mark.lewis@mir3.com
  Subject: Re: Delete query takes exorbitant amount of time
  In-Reply-To: <Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su>
  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> <Pine.GSO.4.62.0503250837140.17555@ra.sai.msu.su>

* 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