From: Michael Glaesemann <grzm@seespotcode.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: EXPLAIN ANALYZE time calculations
Date: Sun, 2 Dec 2007 20:06:07 -0500
Message-ID: <B7887A14-4EA8-4027-AAFB-FE44E35E4046@seespotcode.net> (raw)
In-Reply-To: <239.1196643379@sss.pgh.pa.us>
References: <8C0EE80A-42A3-4CC1-850B-2A6B9220B422@seespotcode.net>
<239.1196643379@sss.pgh.pa.us>
On Dec 2, 2007, at 19:56 , Tom Lane wrote:
> IOW the actual time to get in and out of a node is going to be a
> shade more
> than is reported.
Thanks, Tom. Should be close enough for jazz.
When I was first going over the Using Explain section, I stumbled a
bit on the startup time/total time/loops bit (which is why explain-
analyze.info times and percentages are currently miscalculated). I
took startup time to be the time to return the first row *of the
first loop*. But it's actually the average startup time to return the
first row *in each loop*, right?
Michael Glaesemann
grzm seespotcode net
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: grzm@seespotcode.net, tgl@sss.pgh.pa.us
Subject: Re: EXPLAIN ANALYZE time calculations
In-Reply-To: <B7887A14-4EA8-4027-AAFB-FE44E35E4046@seespotcode.net>
References: <8C0EE80A-42A3-4CC1-850B-2A6B9220B422@seespotcode.net> <239.1196643379@sss.pgh.pa.us> <B7887A14-4EA8-4027-AAFB-FE44E35E4046@seespotcode.net>
* 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