From: | Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 |
Date: | 2003-08-21 21:51:42 |
Message-ID: | 200308212351.42464.ftm.van.vugt@foxi.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Frank van Vugt | 2003-08-21 23:03:44 | Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 |
Previous Message | Stephan Szabo | 2003-08-21 21:29:54 | Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-21 21:56:02 | Re: Decent VACUUM (was: Buglist) |
Previous Message | Tom Lane | 2003-08-21 21:46:03 | Re: [SQL] "SELECT IN" Still Broken in 7.4b |