That makes a lot of sense. Sure enough, if I change the query from WHERE x > 0 (which return a lot of rows) to WHERE x > 0 AND x < 1 I now get an index scan.
> As for why you see index usage in your first example query and not your > second: compare the number of rows in question. An index is extremely > useful if 19 rows will be returned. But when 62350411 rows will be > returned, you're talking about a substantial fraction of the table. A > sequential scan will probably correctly be judged to be faster by the > planner. > ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
