Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 - Mailing list pgsql-bugs

From Frank van Vugt
Subject Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Date
Msg-id 200308212351.42464.ftm.van.vugt@foxi.nl
Whole thread Raw
In response to Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
List pgsql-bugs
> What's your time zone setting?
> Also, are you using --enable-integer-datetimes?

I'm running Slack v8 (with some updates, but still), so TZ is not defined as
environment variable, but it's using 'Europe/Amsterdam'.

I've verified whether setting TZ made a difference (stop/starting the server),
it didn't.

Also, it was NOT configured with integer datetimes:

~$head /usr/src/postgresql/config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by PostgreSQL configure 7.4beta1, which was
generated by GNU Autoconf 2.53.  Invocation command line was

  $ ./configure --with-openssl --with-perl --with-python --with-tcl


I've verified this behaviour on a second machine (AMD instead of Intel) which
was configured with the same options and got the same result

select version();
                                version
------------------------------------------------------------------------
 PostgreSQL 7.4beta1 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66




Best,




Frank.

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Next
From: Frank van Vugt
Date:
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12