| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christian Holtje" <christian(dot)holtje(at)timesys(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #2366: Timestamptz data type is inaccurate |
| Date: | 2006-03-31 23:48:07 |
| Message-ID: | 5491.1143848887@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Christian Holtje" <christian(dot)holtje(at)timesys(dot)com> writes:
> I don't know what's going on, but basically, for some dates timestamptz is
> loosing parts of the date/time (like the timezone, etc.)
> db=# select '2076-03-30 19:57:05-05'::timestamptz;
> timestamptz
> ---------------------
> 2076-03-31 00:57:05
> (1 row)
That date is probably outside the range of dates for which your OS knows
the timezone rules. If you were using PG 8.0 or later, this would
actually be our fault, because 8.0 contains its own timezone database
... but 7.4 is at the mercy of the OS's timezone library.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Ellis | 2006-04-01 23:55:17 | BUG #2369: pg_dump function dependencies |
| Previous Message | Alvaro Herrera | 2006-03-31 23:43:18 | Re: BUG #2366: Timestamptz data type is inaccurate |