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

From Martijn van Oosterhout
Subject Re: Strange behaviour of SELECT ... IN
Date
Msg-id 20020627092847.B11046@svana.org
Whole thread Raw
In response to Re: Strange behaviour of SELECT ... IN  (Jorge Sarmiento <jsarmiento@ccom.org>)
Responses Re: Strange behaviour of SELECT ... IN  (Jorge Sarmiento <jsarmiento@ccom.org>)
List pgsql-general
On Wed, Jun 26, 2002 at 04:00:08PM -0400, Jorge Sarmiento wrote:
> uh...
>
> the first one is an INDEX SCAN, the second one a SEQUENTIAL SCAN.
>
> number of rows in table has nothing to do...

Wrong. The number of rows has everything to do with it. If the number of
rows exceeds 50% of the table, a sequential scan is faster than an index
scan.

You can use enable_seq_scan=off to force it. Let us know if the index scan
is actually significantly faster.

Oh, you did use VACUUM ANALYZE right?

--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.



pgsql-general by date:

Previous
From: d a
Date:
Subject: Deadlock error when inserting single row
Next
From: "Jeff MacDonald"
Date:
Subject: Re: Advocacy Idea.