Re: abstime bug

Michael Fuhr wrote:
> 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.

Yea, I see the same thing in 8.0.X. I don't think abstime should be
used in that date range, timestamp is a better solution.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073