"Dr. Stephane Schildknecht" <sschildknecht@linagora.com> writes:
> Tom Lane wrote:
>> It doesn't. It returns "invalid" and "infinity".
> Is there a reason for this ?
I suppose the "invalid" value is a legacy thing, but "infinity"
certainly strikes me as useful. We have that in the regular
timestamp type as well.
If you're asking why those particular encoded values, I dunno.
Certainly it seems like "infinity" needs to be larger than all
normal values so you don't have to special-case it in comparisons.
regards, tom lane
