pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Cc: Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Index scan startup time
Date: Thu, 30 Mar 2006 14:51:47 +0200
Message-ID: <20060330125147.GA13611@uio.no> (raw)
In-Reply-To: <20060330124251.GK6811@mathom.us>
References: <200603301359.11038.peter_e@gmx.net>
	<20060330120206.GA13075@uio.no>
	<200603301423.54510.peter_e@gmx.net>
	<20060330123134.GA13408@uio.no>
	<20060330124251.GK6811@mathom.us>

On Thu, Mar 30, 2006 at 07:42:53AM -0500, Michael Stone wrote:
> Yes. And the estimates are bad enough (orders of magnitude) that I can't 
> help but wonder whether pg could come up with a better plan with better 
> statistics:
> 
>>>>>  ->  Index Scan using activity_pk on activity  (cost=0.00..40717259.91 
>>>>>  rows=6538650 width=8) (actual time=207356.050..207356.722 rows=100 
>>>>>  loops=1) Filter: ((state = 10000) OR (state = 10001))

Isn't the rows=100 here because of the LIMIT?

/* Steinar */
-- 
Homepage: http://www.sesse.net/



view thread (16+ messages)  latest in thread

Message-ID: <20060330125147.GA13611@uio.no>
Permalink:  ../20060330125147.GA13611@uio.no/
Also on:    postgresql.org/message-id/20060330125147.GA13611@uio.no

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: sgunderson@bigfoot.com, peter_e@gmx.net
  Subject: Re: Index scan startup time
  In-Reply-To: <20060330125147.GA13611@uio.no>

* 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