> Is this a bug that the index doesn't work on floats or is it a
> datatype mismatch thing?
> Seq Scan on foo (cost=0.00 size=0 width=8)
Likely neither. Notice the cost of a sequential scan; it is zero. Why
bother doing an index scan?
You need at least two more things to happen to provoke Postgres into
using your index:
1) Have more entries in the table; rule of thumb is O(100) before an
index will be used.
2) Run vacuum after getting that many entries to make sure the optimizer
will know about the configuration of the tables and indices.
Good luck.
- Tom
