Re: Follow up: range query with timestamp returns different result with index than without (7.3.3)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christian van der Leeden <lists(at)logicunited(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Follow up: range query with timestamp returns different result with index than without (7.3.3)
Date: 2003-08-07 14:23:16
Message-ID: 15202.1060266196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christian van der Leeden <lists(at)logicunited(dot)com> writes:
> the reason for this misbehaviour was an invalid timestamp value.
> I've tried to dump/restore the db and the restore choked on a
> "incorrect timestamp" namely:
> 4714-11--2147483624 -2147483648:-2147483648:-2147483648 BC

Hmm ... I'm suspecting that that was a "minus infinity" under the hood.
Is your installation built with integer timestamps, or floating point?
(If you're not sure, try "pg_config --configure" and see if it mentions
--enable-integer-datetimes.) Also, is the column in question of type
timestamp, or timestamp with time zone?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2003-08-07 15:23:41 Re: Non-standard TIMESTAMP WITH TIME ZONE literal handling
Previous Message Tom Lane 2003-08-07 14:06:35 Re: range query with timestamp returns different result with index than without (7.3.3)