pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Michael Stone <mstone+postgres@mathom.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Index scan startup time
Date: Thu, 30 Mar 2006 10:24:23 -0500
Message-ID: <14952.1143732263@sss.pgh.pa.us> (raw)
In-Reply-To: <200603301716.13840.peter_e@gmx.net>
References: <200603301359.11038.peter_e@gmx.net>
	<20060330132915.GL6811@mathom.us>
	<14358.1143728757@sss.pgh.pa.us>
	<200603301716.13840.peter_e@gmx.net>

Peter Eisentraut <peter_e@gmx.net> writes:
> So from when to when is the startup time (the "x" in "x..y") actually 
> measured?  When does the clock start ticking and when does it stop?  
> That is what's confusing me.

The planner thinks of the startup time (the first estimated-cost number)
as the time before the output scan can start, eg, time to do the sort in
a sort node.  EXPLAIN ANALYZE however reports the actual time until the
first output row is delivered.  When you've got a filter applied to the
node result, as in this case, there can be a material difference between
the two definitions, because of the time spent scanning rows that don't
get past the filter.

			regards, tom lane



view thread (16+ messages)  latest in thread

Message-ID: <14952.1143732263@sss.pgh.pa.us>
Permalink:  ../14952.1143732263@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14952.1143732263@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 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: tgl@sss.pgh.pa.us, peter_e@gmx.net, mstone+postgres@mathom.us
  Subject: Re: Index scan startup time
  In-Reply-To: <14952.1143732263@sss.pgh.pa.us>
  References: <200603301359.11038.peter_e@gmx.net> <20060330132915.GL6811@mathom.us> <14358.1143728757@sss.pgh.pa.us> <200603301716.13840.peter_e@gmx.net> <14952.1143732263@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