From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Teran <david.teran@cluster9.com>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: another query optimization question
Date: Fri, 30 Jan 2004 14:19:26 -0500
Message-ID: <17545.1075490366@sss.pgh.pa.us> (raw)
In-Reply-To: <F8B3002A-5350-11D8-9392-000A95A6F0DC@cluster9.com>
References: <32DEEB93-534E-11D8-9392-000A95A6F0DC@cluster9.com>
<20040130100845.E58632@megazone.bigpanda.com>
<F8B3002A-5350-11D8-9392-000A95A6F0DC@cluster9.com>
David Teran <david.teran@cluster9.com> writes:
> [ query plan ]
I got a little distracted by the bizarre actual-time values shown for
some of the query steps:
> -> Merge Join (cost=2451266.53..2655338.83 rows=13604393 width=8)
> (actual time=82899.466..-2371037.726 rows=2091599 loops=1)
> -> Sort (cost=2451169.10..2483246.47 rows=12830947 width=8)
> (actual time=82891.076..-529619.213 rows=4187378 loops=1)
> -> Hash IN Join (cost=507.32..439065.37 rows=12830947
> width=8) (actual time=61.943..1874640.807 rows=4187378 loops=1)
The hash-join total time is obviously wrong seeing that the total
runtime is only about 100000 msec, and the negative values for the other
two are even more obviously wrong.
I recall that we saw similar symptoms once before, and I thought we'd
fixed it, but I didn't find any relevant mentions in the CVS logs.
What version are you running, exactly? Could you repeat the EXPLAIN
with client_min_messages set to 'debug2', and see if you see any
messages about InstrStartTimer or InstrStopNode?
regards, tom lane
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, david.teran@cluster9.com, sszabo@megazone.bigpanda.com
Subject: Re: another query optimization question
In-Reply-To: <17545.1075490366@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