Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-performance by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group