X-Original-To: pgsql-hackers-win32-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2CAC3D8FF7 for ; Thu, 15 Sep 2005 14:00:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 78237-05 for ; Thu, 15 Sep 2005 17:00:13 +0000 (GMT) Received: from trolak.mydnsbox2.com (ns1.mydnsbox2.com [207.44.142.118]) by svr1.postgresql.org (Postfix) with ESMTP id B3A7CD8FEC for ; Thu, 15 Sep 2005 14:00:12 -0300 (ADT) Received: from [192.168.1.103] (cpe-024-211-165-134.nc.res.rr.com [24.211.165.134]) (authenticated (0 bits)) by trolak.mydnsbox2.com (8.11.6/8.11.6) with ESMTP id j8FGG2u11609; Thu, 15 Sep 2005 11:16:02 -0500 Message-ID: <4329A88A.6050308@dunslane.net> Date: Thu, 15 Sep 2005 12:59:54 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.3.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lane Van Ingen Cc: Tom Lane , pgsql-hackers-win32@postgresql.org Subject: Re: Server Time Setting References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.04 required=5 tests=[AWL=0.040] X-Spam-Level: X-Archive-Number: 200509/32 X-Sequence-Number: 3398 Lane Van Ingen wrote: >If I am following this correctly, I may have solved the problem for myself >in >the Eastern time zone, but this application gets deployed around the world, >anywhere at sea that a vessel can go. While I think the vessel sets its time >based on its home port and keeps it that way through voyage(s), I am won- >dering if handling of time is still going to give me problems outside of >time >zones where DST is being observed. > > > > If they set the machine to the home port's time and leave it there that should be no problem, as long as they select DST adjustment if it's a zone that uses DST. In fact I suspect they can set it anyway, regardless of TZ, because if the zone doesn't have DST nothing should happen. Test it and see. The trouble with any sort of detection/correction would be that if the DST flag is off we have no idea whether the user has left the time on the zone's base and so it shows an hour's difference from actual local time, or if they have set it to the DST time manually and thus more or less lied about the value of UTC. I've seen both happen, many times. cheers andrew