Neil Conway <[EMAIL PROTECTED]> writes:
> * add a TODO item for considering changing how equality comparisons
> treat NaN values, per recent discussion
Seems like a complete nonstarter, unfortunately. btree requires the
datatype to have a total order, and I can't see that changing, so NaN
loses.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
