Re: seq scan on a table whereas an index exist

Nicolas GIMMILLARO <Nicolas(dot)GIMMILLARO(at)wmi(dot)fr> writes:
> What's wrong with my "select * from web_access where date between
> '01/01/2001' and '06/03/2001' " query ?

Nothing. The planner is estimating that this query will retrieve a
sufficiently large fraction of the rows in the table that a seqscan
will be cheaper than an indexscan. That estimate might or might not
be correct, but it's operating as designed.

The form with the subselects confuses the planner enough that it falls
back on default selectivity estimates, which do lead it to choose an
indexscan.

regards, tom lane