Using a seqscan to retrieve half of the entries in a table is not a bug,
it is correct behavior.
Your test case might make you think otherwise, but that's because your
test data is artificially well-ordered. Try the two methods with the
same data loaded in a random order ...
Marcin Zukowski ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Not using indexes in WHERE clauses
Long Description
PGSQL doesn't use indexes in WHERE clauses.
Tested on version 7.0.3:
PostgreSQL 7.0.3 on i586-pc-linux-gnu, co
