| From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problems with timestamp with time zone and old dates? |
| Date: | 2012-08-21 21:50:59 |
| Message-ID: | 503402C3.3090504@pinpointresearch.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/21/2012 02:29 PM, Michael Clark wrote:
> Hello all,
>
> I have a weird situation I am trying to work through, and could use
> some help if anyone can provide some.
>
> I have a table with a column to store timestamp with time zone, and
> when I store an older take (before 1895 or so), the value I get back
> from PG when doing a select seems odd and is causing my client some
> issues with the format string.
>
> 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 the odd offset that is causing my client problems, and I was
> wondering if this is expected?
> (I am using PG9.1.3)
>
> This contrasts:
> INSERT INTO sometable (startdate) values ('2012-08-21 21:17:00+00:00');
>
> I get the following when I select:
> startdate
> ------------------------
> 2012-08-21 17:17:00-04
> (1 row)
>
>
> Can anyone shed some light on if this is expected, or if I am doing
> something odd?
>
> Much appreciated!
> Michael
>
PostgreSQL derives its timezone rules from the Olson database:
http://en.wikipedia.org/wiki/Tz_database.
N.B the offset prior to November 18, 1883.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ondrej Ivanič | 2012-08-21 22:51:57 | Re: redundant fields in table for "performance optimizations" |
| Previous Message | Michael Clark | 2012-08-21 21:29:14 | Problems with timestamp with time zone and old dates? |