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

From Tom Lane
Subject Re: Seq. scan when using comparison operators, why? [netaktiv.com #150]
Date
Msg-id 20548.1018275990@sss.pgh.pa.us
Whole thread Raw
In response to Re: Seq. scan when using comparison operators, why? [netaktiv.com #150]  (Stephane Bortzmeyer <bortzmeyer@netaktiv.com>)
List pgsql-general
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

pgsql-general by date:

Previous
From: Stephane Bortzmeyer
Date:
Subject: Re: Seq. scan when using comparison operators, why? [netaktiv.com #150]
Next
From: John Gibson
Date:
Subject: Help with pg_hba.conf file