Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id D57EF9FB269; Thu, 5 Oct 2006 22:33:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 71087-03; Fri, 6 Oct 2006 01:33:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from proton.planetargon.com (unknown [198.145.37.35]) by postgresql.org (Postfix) with ESMTP id C86049FB208; Thu, 5 Oct 2006 22:33:05 -0300 (ADT) Received: from [172.16.1.101] (unknown [61.197.227.146]) by proton.planetargon.com (Postfix) with ESMTP id 44CA384CFC5; Thu, 5 Oct 2006 18:33:02 -0700 (PDT) In-Reply-To: <21619.1160067054@sss.pgh.pa.us> References: <4522EC42.1080500@refractions.net> <21619.1160067054@sss.pgh.pa.us> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: gdavis@refractions.net, pgsql-sql@postgresql.org, pgsql-hackers@postgresql.org Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: [HACKERS] timestamp subtraction (was Re: formatting intervals with to_char) Date: Fri, 6 Oct 2006 10:32:59 +0900 To: Tom Lane X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/74 X-Sequence-Number: 26463 On Oct 6, 2006, at 1:50 , Tom Lane wrote: > I'm tempted to propose that we remove the justify_hours call, and tell > anyone who really wants the old results to apply justify_hours() to > the > subtraction result for themselves. Not sure what the fallout would > be, > though. I'm tempted to support such a proposal. Is this something that we'd want to do for 8.2? There are some interval range checking fixes I'm working on for 8.3. Perhaps this could be rolled into that as well? Then again, range checking and behavior are two separate things. Considering how late it is in the cycle, perhaps the change in behavior should come in 8.3. Michael Glaesemann grzm seespotcode net