Re: Seq. scan when using comparison operators, why? [netaktiv.com #150] - Mailing list pgsql-general

On Mon, Apr 08, 2002 at 10:15:05AM -0400,
 Tom Lane <tgl@sss.pgh.pa.us> wrote
 a message of 13 lines which said:

> That is the default behavior in the absence of any VACUUM ANALYZE
...
> An indexscan is generally not a win for scanning more than a few
> percent of a table.

You're right, after the VACUUM ANALYZE, both queries use sequential
scan :-)