Re: abstime bug - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: abstime bug
Date
Msg-id 20050722143302.GA19419@winnie.fuhr.org
Whole thread Raw
In response to Re: abstime bug  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: abstime bug  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: abstime bug  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Jul 22, 2005 at 10:15:40AM -0400, Bruce Momjian wrote:
>
> Current CVS shows:
>
>     test=> select '1901/12/14 1:00'::abstime;
>             abstime
>     ------------------------
>      1901-12-14 01:00:00-05
>     (1 row)

Depends on your timezone:

SET TimeZone TO 'US/Eastern';
SELECT '1901/12/14 1:00'::abstime;
        abstime
------------------------
 1901-12-14 01:00:00-05
(1 row)

SET TimeZone TO 'Asia/Hong_Kong';
SELECT '1901/12/14 1:00'::abstime;
        abstime
------------------------
 2038-01-19 07:51:40+08
(1 row)

I'd guess this is due to the 32-bitness of abstime.  Those timestamps
are around the min and max values of a 32-bit timestamp based on the
traditional Unix epoch.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: abstime bug
Next
From: Bruce Momjian
Date:
Subject: Re: abstime bug