From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Lane Van Ingen" <lvaningen(at)ESNCC(dot)com> |
Cc: | "Obe, Regina DND\\MIS" <robe(dot)dnd(at)cityofboston(dot)gov>, pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: Server Time Setting |
Date: | 2005-09-15 15:51:14 |
Message-ID: | 14438.1126799474@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
"Lane Van Ingen" <lvaningen(at)ESNCC(dot)com> writes:
> Looks like I may have just solved my own problem: I noticed that in Date and
> Time Properties of the Windows clock, on the Time Zone tab, there is a
> checkbox
> called "Automatically adjust clock for daylight savings time changes".
> If that box is unchecked, PostgreSQL must try to compensate, because on
> those
> platforms that are unchecked is where I am having the problem of now()
> returning
> a date that is one hour later. It now works correctly.
Hmm. I think the way that the code in pgtz.c is set up, it just assumes
that either "Eastern Standard Time" or "Eastern Daylight Time" should
map to our US/Eastern timezone (which is a DST-aware zone). Running
your system in non-DST-aware mode is what's confusing it --- the offset
to GMT is an hour different than it "should be" at this time of year.
Should pgtz.c try to detect this situation and handle it by mapping to a
non-DST-aware internal timezone?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-09-15 16:07:26 | Re: Server Time Setting |
Previous Message | Lane Van Ingen | 2005-09-15 15:16:56 | Re: Server Time Setting |