Re: Index scan startup time

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Stone <mstone+postgres(at)mathom(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Index scan startup time
Date: 2006-03-30 15:16:13
Message-ID: 200603301716.13840.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-performance

Tom Lane wrote:
> The problem here appears to be a non-random correlation between state
> and activity, such that the desired state values are not randomly
> scattered in the activity sequence. The planner doesn't know about
> that correlation and hence can't predict the poor startup time.

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.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2006-03-30 15:19:13 Re: CREATE INDEX rather sluggish
Previous Message Dave Dutcher 2006-03-30 14:34:23 Re: [Solved] Slow performance on Windows .NET and OleDb