| From: | Tony Theodore <tony(dot)theodore(at)gmail(dot)com> |
|---|---|
| To: | Tim Uckun <timuckun(at)gmail(dot)com> |
| Cc: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timestamp with and without timezone conversion confusion. |
| Date: | 2013-10-02 09:05:02 |
| Message-ID: | 545346BE-47FC-4391-B59A-1EE6F288088E@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/10/2013, at 6:49 PM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
> >The reason for that is that in PostgreSQL there is no time zone
> information stored along with a "timestamp with time zone",
> it is stored in UTC.
>
> That seems unintuitive. What is the difference between timestamp without time zone and timestamp with time zone? I was expecting to have the time zone stored in the field. For example one row might be in UTC but the other row might be in my local time.
>
> Maybe the question I need to ask is "how can I store the time zone along with the timestamp"
>
> >That is because AT TIME ZONE returns a "timestamp without time zone"
>
> Also seems counterintutive but I guess I can aways convert it. I am just not getting the right offset when I convert. That's what's puzzling.
Here's a handy blog post from Josh Berkus about timestamps:
http://it.toolbox.com/blogs/database-soup/zone-of-misunderstanding-48608
Cheers,
Tony
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Uckun | 2013-10-02 09:15:49 | Re: Timestamp with and without timezone conversion confusion. |
| Previous Message | Tim Uckun | 2013-10-02 08:49:38 | Re: Timestamp with and without timezone conversion confusion. |