Re: abstime bug

Michael Fuhr <mike@fuhr.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