pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Guenzl, Martin <martin@guenzl.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help with EXPLAIN ANALYZE runtimes
Date: Sun, 09 Jan 2005 00:23:42 -0500
Message-ID: <24309.1105248222@sss.pgh.pa.us> (raw)
In-Reply-To: <200501090444.j094ideg019542@mail01.syd.optusnet.com.au>
References: <200501090444.j094ideg019542@mail01.syd.optusnet.com.au>

"Guenzl, Martin" <martin@guenzl.com> writes:
> On the latter, the EXPLAIN ANALYZE returned what I thought was a strange
> result - here is the excerpt ...

Do you think we are psychics who can guess at your problem when you've
shown us none of the table definitions, none of the query, and only a
small part of the EXPLAIN output?

Donning my Karnak headgear, I will guess that this is actually not a
SELECT query but some kind of update operation, and that the time
sink is in the updating part and not in the data extraction part.
(Inefficient foreign-key operations would be a likely cause, as would
poorly written user-defined triggers.)  But that's strictly a guess.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <24309.1105248222@sss.pgh.pa.us>
Permalink:  ../24309.1105248222@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24309.1105248222@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, martin@guenzl.com
  Subject: Re: Help with EXPLAIN ANALYZE runtimes
  In-Reply-To: <24309.1105248222@sss.pgh.pa.us>

* 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