Re: abstime bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, jw <jw(at)sduept(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: abstime bug
Date: 2005-07-22 19:57:04
Message-ID: 16037.1122062224@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Fuhr <mike(at)fuhr(dot)org> writes:
> 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.

Fixed in CVS tip:

regression=# SET TimeZone TO 'Asia/Hong_Kong';
SET
regression=# SELECT '1901/12/14 1:00'::abstime;
abstime
---------
invalid
(1 row)

Doesn't seem important enough to back-patch, though.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Smith 2005-07-23 09:59:48 BUG #1781: result of cascading triggers not available until function exits.
Previous Message Kris Jurka 2005-07-22 19:40:29 Re: [JDBC] BUG #1780: JDBC driver "setNull" throws for BLOB