Re: Seq. scan when using comparison operators, why? [netaktiv.com #150]

Stephane Bortzmeyer <bortzmeyer@netaktiv.com> writes:
> You're right, after the VACUUM ANALYZE, both queries use sequential
> scan :-)

Try it with a bigger table ;-).  On a toy-size table the planner doesn't
see any reason to bother with an index at all; the index cannot save any
disk fetches when there's only one or two disk pages in the table anyway
...

            regards, tom lane