X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 79A3BD1B542 for ; Thu, 4 Mar 2004 18:36:32 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 87543-07 for ; Thu, 4 Mar 2004 14:36:29 -0400 (AST) Received: from mail.dhs-club.com (mail.dhs-club.com [63.124.98.242]) by svr1.postgresql.org (Postfix) with ESMTP id B6FC7D1B4C3 for ; Thu, 4 Mar 2004 14:36:27 -0400 (AST) Received: from dhs-club.com ([192.168.0.3]) (authenticated) by mail.dhs-club.com (8.11.6/8.11.3) with ESMTP id i24IaRb00413 for ; Thu, 4 Mar 2004 10:36:27 -0800 Message-ID: <40477806.8B5F7E60@dhs-club.com> Date: Thu, 04 Mar 2004 13:40:06 -0500 From: DHS Webmaster Organization: The DHS Club X-Mailer: Mozilla 4.79 [en]C-CCK-MCD compaq (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Cc: pgsql-admin Subject: Re: bizarre AGE behaviour References: <40461395.5324CFEE@dhs-club.com> <200403031000.05524.scrawford@pinpointresearch.com> <19029.1078355959@sss.pgh.pa.us> <200403040857.39605.scrawford@pinpointresearch.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/24 X-Sequence-Number: 12594 You are both right. Your explanation, Steve, was the light that got me going on a simpler solution along the lines of what Tom suggested. I didn't really need AGE, and upon digging in, couldn't even remember why I had chosen that in the first place. Postgres is the bomb! Thanks guys. Steve Crawford wrote: > > On Wednesday 03 March 2004 3:19 pm, Tom Lane wrote: > > Steve Crawford writes: > > > US Daylight Saving Time starts this year on April 4 when 0200 > > > jumps to 0300. The answers PostgreSQL gave are correct. > > > > I suspect what the OP wants is non-timezone-aware behavior... > > You are probably right. In his original post he posited that the > problem was due to some sort of leap-year bug in PostgreSQL. I was > just pointing him to the real cause of his observations so he could > tackle whatever problem he was having secure in the knowledge that PG > was working correctly. > > Cheers, > Steve > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match -- Bill MacArthur Webmaster The DHS Club, Inc. The Best Is Yet To Come!