Re: Strange behaviour of SELECT ... IN - Mailing list pgsql-general

From Stephan Szabo
Subject Re: Strange behaviour of SELECT ... IN
Date
Msg-id 20020626141106.M96143-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: Strange behaviour of SELECT ... IN  (Jorge Sarmiento <jsarmiento@ccom.org>)
List pgsql-general
On Wed, 26 Jun 2002, Jorge Sarmiento wrote:

> the first one is an INDEX SCAN, the second one a SEQUENTIAL SCAN.
>
> number of rows in table has nothing to do...

Sure it does.  As the number of rows selected approaches the number
of rows in the table the cost of the index scan relative to sequential
scan can increase due to the fact that we're reading both the index
and the heap blocks (for row validity testing - and doing it in a
possibly random order) as opposed to a sequential read set of the heap.




pgsql-general by date:

Previous
From: Jorge Sarmiento
Date:
Subject: Re: Strange behaviour of SELECT ... IN
Next
From: Andrew Sullivan
Date:
Subject: Re: Advocacy Idea.