| From: | Matteo Beccati <php(at)beccati(dot)com> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Odd behaviour of timestamptz |
| Date: | 2007-02-21 08:46:40 |
| Message-ID: | 45DC06F0.8060703@beccati.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Michael Glaesemann wrote:
>> test=# SELECT * from test;
>> data
>> ----------------------------
>> 1910-01-10 00:00:00+00:19:32
>> 1990-01-10 00:00:00+01
>> (2 rows)
>
> I suspect your RPMs build PostgreSQL without --enable-integer-datetimes.
> Without this configure flag, timestamps are represented as floats, with
> all of the imprecision that implies. See the second note below the
> Date/Time Types table:
>
> http://www.postgresql.org/docs/8.2/interactive/datatype-datetime.html#DATATYPE-DATETIME-TABLE
In fact I was thinking to the opposite, but at least one of them didn't
use --enable-integer-datetimes. I could understand problems representing
microseconds, but not the time zone...
Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-02-21 08:53:00 | Re: Error upgrading on W2K |
| Previous Message | Matteo Beccati | 2007-02-21 08:40:05 | Re: Odd behaviour of timestamptz |