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

Re: Index scan startup time

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: "Steinar H(dot) Gunderson" <sgunderson(at)bigfoot(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Index scan startup time
Date: 2006-03-30 12:59:02
Message-ID: 200603301459.03011.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-performance
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/

In response to

Responses

pgsql-performance by date

Next:From: Steinar H. GundersonDate: 2006-03-30 13:00:41
Subject: Re: Index scan startup time
Previous:From: Steinar H. GundersonDate: 2006-03-30 12:51:47
Subject: Re: Index scan startup time

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