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

Hi,

I've put the database dump here:
http://www.vanderleeden.de/test/databasedumps.tar
(about 16 MB)

It contains the ascii dump of pg_dump and the
pg_dump --format c of the database.

I've only got the dumps left of the original problem,
since during my tries to remedy the problem
(upgrade to 7.3.4 with initdb and restore)
the restore failed and I don't have the original
db saved...

The db itself (only speaking for the current 7.3.4 build),
is not configured with enabled-integer-datetimes.
Creation date is defined as:
creation_date | timestamp without time zone | not null

CU

Christian

On Thursday, August 7, 2003, at 04:23 PM, Tom Lane wrote:

> 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
>
----------------------------------------------
Christian van der Leeden
Logic United GmbH
Tel: 089-189488-66 Mob: 0163-3747111
www.logicunited.com