Re: Index scan startup time

Am Donnerstag, 30. März 2006 14:31 schrieb Steinar H. Gunderson:
> Well, it's logical enough; it scans along activity_id until it finds one
> with state=10000 or state=10001. You obviously have a _lot_ of records with
> low activity_id and state none of these two, so Postgres needs to scan all
> those records before it founds 100 it can output. This is the “startup
> cost” you're seeing.

The startup cost is the cost until the plan is set up to start outputting
rows.  It is not the time until the first row is found.

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