From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Michael Clark <codingninja(at)gmail(dot)com> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Problems with timestamp with time zone and old dates? |
Date: | 2012-08-22 09:00:36 |
Message-ID: | 20120822090036.GA9881@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 21, 2012 at 05:29:14PM -0400, Michael Clark wrote:
> For example, if I insert like so:
> INSERT INTO sometable (startdate) values ('1750-08-21 21:17:00+00:00');
>
> I get the following when I select:
> SELECT startdate FROM sometable;
> startdate
> ------------------------------
> 1750-08-21 15:59:28-05:17:32
> (1 row)
It's impossible to tell without knowing what is your time zone, but
I don't see anything particularly strange about it. Non-integer offsets
do happen, and in the past there were more commonly used.
Based on what I can see in timezone data, it looks that time zone
America/Toronto
used this offset until 1895.
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2012-08-22 10:00:40 | Re: How hard would a "path" operator be to implement in PostgreSQL |
Previous Message | Albe Laurenz | 2012-08-22 08:52:08 | Re: Understanding autocommit |