From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
---|---|
To: | "maxxedev maxxedev" <maxxedev(at)gmail(dot)com>,pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgres timestamp data errors |
Date: | 2012-11-30 13:08:06 |
Message-ID: | 20121130130807.69320@gmx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
maxxedev maxxedev wrote:
> db=# show timezone;
> TimeZone
> ----------
> Eire
> (1 row)
> db=# insert into test_table values('1912-03-14 00:00:00.000000 -0025');
> INSERT 0 1
> db=# select * from test_table;
> invoice_date
> ------------------------------
> 1912-03-13 23:59:39-00:25:21
> (1 row)
>
>
> Note that inserted timestamp and stored timestamps are logically
> equivalent. However, why does SELECT show the timestamp in a timezone
> offset with minute precision?
Because in 1913, that was the offset between Dublin time and GMT.
http://www.velocityreviews.com/forums/t372817-timestamp-and-the-eire-timezone.html
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Henry Drexler | 2012-11-30 13:22:07 | query performance, though it was timestamps,maybe just table size? |
Previous Message | Piviul | 2012-11-30 12:08:24 | SETOF come ritorno delle funzioni |