| From: | Michael Fuhr <mike(at)fuhr(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | jw <jw(at)sduept(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: abstime bug |
| Date: | 2005-07-22 14:33:02 |
| Message-ID: | 20050722143302.GA19419@winnie.fuhr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-07-22 14:44:03 | Re: abstime bug |
| Previous Message | Bruce Momjian | 2005-07-22 14:15:40 | Re: abstime bug |