From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Andrew Chernow <ac(at)esilo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Odd timezone backend output |
Date: | 2008-05-01 15:14:13 |
Message-ID: | 4819DE45.9070704@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Chernow wrote:
> 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.
>
>
The only file times we should ever be interested in are surely epoch
times, which should be unaffected by time zones.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-05-01 15:26:21 | Re: Protection from SQL injection |
Previous Message | Gregory Stark | 2008-05-01 15:07:08 | Re: Protection from SQL injection |