From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Christian Holtje <christian(dot)holtje(at)timesys(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #2366: Timestamptz data type is inaccurate |
Date: | 2006-03-31 23:43:18 |
Message-ID: | 20060331234318.GC18914@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Christian Holtje wrote:
> I don't know what's going on, but basically, for some dates timestamptz is
> loosing parts of the date/time (like the timezone, etc.)
>
> db=# select '2076-03-30 19:57:05-05'::timestamptz;
> timestamptz
> ---------------------
> 2076-03-31 00:57:05
> (1 row)
Timestamp support went under a big rewrite for 8.0. The problem doesn't
present there. I suggest you upgrade; the code in 7.4 is probably buggy
enough that it would be a difficult proposition to fix the bug there.
That said, maybe you could try with the --enable-integer-datetimes flag
to configure -- if you are lucky the bugs are not in that code path.
But I wouldn't count on it.
(I can reproduce the bug here; my 7.4 build has floating point
datetimes.)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-31 23:48:07 | Re: BUG #2366: Timestamptz data type is inaccurate |
Previous Message | Tom Lane | 2006-03-31 17:27:04 | Re: log xid with duration |