Re: Collation order for btree-indexable datatypes

> A closely related problem is that the "current time" special value
> supported by several of the date/time datatypes is inherently not
> compatible with being indexed, since its sort order relative to
> ordinary time values keeps changing.  We had discussed removing this
> special case, and I think agreed to do so, but it hasn't happened yet.
> 
> What I'm inclined to do is force consistency of the comparison operators
> now (for 7.1.1) and then remove "current time" for 7.2, but perhaps it'd
> be better to leave the whole can of worms alone until 7.2.  Comments
> anyone?

Comparing NaN/Invalid seems so off the beaten path that we would just
wait for 7.2.  That and no one has reported a problem with it so far.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026