DST problem on Windows Server
A client has PostgreSQL 8.2.1 installed on a Windows 2000 server.
The time on the server is correct but PostgreSQL is returning a time 1 hour in advance. In other words, it the server time is 1:00 pm, PostgreSQL is returning 2:00 pm. Both the PostgreSQL server and Windows server have been rebooted, but the problem remains.
postgresql.conf is using the default timezone setting:
#timezone = unknown # actually, defaults to TZ
# environment setting
and the time zone setting on the Windows server is (GMT - 6) Cental Time (US and Canada), which is the correct location.
Any suggestions how to resolve this, or why its happening?
George
George Weaver wrote:
A client has PostgreSQL 8.2.1 installed on a Windows 2000 server.
W2K has been EOL'ed for quite some time. You might want to stress that to your
client. I don't know what you bill per hour, but their not-upgrading cost
savings should be negative and keep climbing.
Did you even look at
http://blogs.msdn.com/securitytipstalk/archive/2007/01/25/don-t-let-your-computer-fall-behind.aspx
You can fix it manually if you read the part about w2k.
George Weaver wrote:
A client has PostgreSQL 8.2.1 installed on a Windows 2000 server.
The time on the server is correct but PostgreSQL is returning a time 1
hour in advance. In other words, it the server time is 1:00 pm,
PostgreSQL is returning 2:00 pm. Both the PostgreSQL server and Windows
server have been rebooted, but the problem remains.postgresql.conf is using the default timezone setting:
#timezone = unknown # actually, defaults to TZ
# environment settingand the time zone setting on the Windows server is (GMT - 6) Cental
Time (US and Canada), which is the correct location.Any suggestions how to resolve this, or why its happening?
It could be that it's mis-detecting the OS timezone - is the OS even
updated for the new DST rules? I thought they didn't release such
patches for win2k unless you paid a bunch extra for it?
Anyway, try hardcoding the timezone value in postgresql.conf to whatever
zone you're in, and see if that solves it.
//Magnus
Date: Wed, 14 Mar 2007 20:39:17 +0100
From: Magnus Hagander <magnus@hagander.net>
To: George Weaver <gweaver@shaw.ca>
Cc: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: DST problem on Windows Server
Message-ID: <45F84F65.5090303@hagander.net>
George Weaver wrote:
A client has PostgreSQL 8.2.1 installed on a Windows 2000 server.The time on the server is correct but PostgreSQL is returning a time 1
hour in advance. In other words, it the server time is 1:00 pm,
PostgreSQL is returning 2:00 pm. Both the PostgreSQL server and Windows
server have been rebooted, but the problem remains.postgresql.conf is using the default timezone setting:
#timezone = unknown # actually, defaults to TZ
# environment settingand the time zone setting on the Windows server is (GMT - 6) Cental
Time (US and Canada), which is the correct location.Any suggestions how to resolve this, or why its happening?
It could be that it's mis-detecting the OS timezone - is the OS even
updated for the new DST rules? I thought they didn't release such
patches for win2k unless you paid a bunch extra for it?
Anyway, try hardcoding the timezone value in postgresql.conf to whatever
zone you're in, and see if that solves it.
//Magnus
George,
We had to run a special utility from Windows on all our Win2k clients and
servers to reset the time zone. The file is called TZEDIT.exe date
12/2/1999 and I think our network admin downloaded it from Microsoft. It
lets you reset the dates that the DST takes place.
I will email instructions our admin put together in a separate email to
you so the file doesn't go to the list.
I saw what happened on my machine if this utility wasn't used. I could set
my clock to the correct time but any files I used on another server showed
the time as being a hour off, even though the problem was on my computer.
When mine was correct the time showing from other servers was correct.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
*** ***
Margaret Gillon, IS Dept., Chromalloy Los Angeles, ext. 297
This e-mail message and any attachment(s) are for the sole use of the
intended recipient(s) and may contain proprietary and/or confidential
information which may be privileged or otherwise protected from
disclosure. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient(s), please contact the
sender by reply email and destroy the original message and any copies of
the message as well as any attachment(s) to the original message.
Import Notes
Resolved by subject fallback