From owner-freebsd-questions@FreeBSD.ORG Wed Jul 28 19:43:45 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E79431065676 for ; Wed, 28 Jul 2010 19:43:45 +0000 (UTC) (envelope-from mginsburg@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 4F9788FC19 for ; Wed, 28 Jul 2010 19:43:45 +0000 (UTC) Received: from [192.168.2.98] (treadshot.ws.pitbpa0.priv.collaborativefusion.com [192.168.2.98]) (AUTH: LOGIN mginsburg, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Wed, 28 Jul 2010 15:43:44 -0400 id 0003F419.000000004C508870.00003C41 Message-ID: <4C508870.6000208@collaborativefusion.com> Date: Wed, 28 Jul 2010 15:43:44 -0400 From: Mike Ginsburg User-Agent: Thunderbird 2.0.0.21 (X11/20090404) MIME-Version: 1.0 To: Jon Radel References: <4C5076D7.5040605@collaborativefusion.com> <4C507AAB.8000709@radel.com> In-Reply-To: <4C507AAB.8000709@radel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Timestamp + Interval time zone issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 19:43:46 -0000 Jon Radel wrote: > On 7/28/10 2:28 PM, Mike Ginsburg wrote: >> >> So I have pg 8.4.3 installed, with a database set to EST5EDT time zone. >> >> When I run "SELECT NOW()" I get >> 07/28/2010 14:27:07.767286 EDT >> >> showing that the timezone is properly set up. >> >> When I then try to add an interval to a statically entered time >> stamp, it gets all strange: >> SELECT '01/03/2011 16:00:00-04'::timestamp with time zone + '-1 >> hour'::interval; >> ?column? ------------------------- >> 01/03/2011 14:00:00 EST >> >> Any idea why the adding of the interval is converting the result into >> EST instead of EDT? > Because Daylight Saving Time will be over by 1/3/2011? Does it still > happen if you use a > statically entered time stamp that's during Daylight Saving? Well now I just feel dumb. Using the same query, but within daylight savings produces the expected result. Thanks for the help. Mike Ginsburg Collaborative Fusion, Inc. mginsburg@collaborativefusion.com