From: | Andrew Chernow <ac(at)esilo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Odd timezone backend output |
Date: | 2008-05-01 14:56:36 |
Message-ID: | 4819DA24.1020909@esilo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Andrew Chernow <ac(at)esilo(dot)com> writes:
>> I am confused about the below results. The backend is in EDT but it is
>> converting timestamps into EST ... excluding NOW(). Regardless of the
>> timezone provided, the backend is dishing out EST.
>
> Try a date that's actually during the EDT part of the year.
>
> regards, tom lane
>
Different systems do different things with Daylight time. For instance:
NTFS adjusts winter file times while in daylight savings (A file time of
Jan 20 6PM reads Jan 20 7PM while in Daylight Time). Whether that is
good or bad is a different story. I don't really have a problem with
either, just needed a little clarity.
Thanks,
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-05-01 15:07:08 | Re: Protection from SQL injection |
Previous Message | Andrew Sullivan | 2008-05-01 14:20:45 | Re: Odd timezone backend output |