Request a Demo
Home   >   mailing lists

Re: index scan on =, but not < ? - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: index scan on =, but not < ?
Date
Msg-id 20050309045519.GA509@decibel.org
Whole thread Raw
In response to Re: index scan on =, but not < ?  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: index scan on =, but not < ?
List pgsql-performance
Tree view 
On Tue, Mar 08, 2005 at 10:38:21PM -0600, Bruno Wolff III wrote:
> Not exactly. If the number of rows to be examined is on the order of 5%
> of the table, an index scan will probably be slower than a sequential
> scan. The visibility issue makes index scans slower in the case that

Shouldn't that be 50%?
--
Jim C. Nasby, Database Consultant               decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why would writes to pgsql_tmp bottleneck at 1mb/s?
Next
From: Bruno Wolff III
Date:
Subject: Re: index scan on =, but not < ?