Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E777E9FB285 for ; Wed, 13 Dec 2006 01:42:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 95165-01 for ; Wed, 13 Dec 2006 01:42:19 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from proton.planetargon.com (unknown [198.145.37.35]) by postgresql.org (Postfix) with ESMTP id 66FE79FA42F for ; Wed, 13 Dec 2006 01:13:41 -0400 (AST) Received: from [172.16.1.106] (unknown [61.197.227.146]) by proton.planetargon.com (Postfix) with ESMTP id 7F20F85F851; Tue, 12 Dec 2006 21:13:37 -0800 (PST) In-Reply-To: <3953.1165940595@sss.pgh.pa.us> References: <1165932562.10968.1.camel@localhost> <457EC53B.2070600@archonet.com> <3953.1165940595@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: Richard Huxton , Cronje Fourie , pgsql-sql@postgresql.org Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: TPCH Benchmark query result invalid Date: Wed, 13 Dec 2006 14:13:34 +0900 To: Tom Lane X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/98 X-Sequence-Number: 27054 On Dec 13, 2006, at 1:23 , Tom Lane wrote: > Richard Huxton writes: >> richardh=# SELECT interval '3' month; >> interval >> ---------- >> 00:00:00 >> (1 row) > >> It's got a zero-length date-range it's comparing against. If you have >> interval '3 months' that should work, but I'm afraid I haven't got >> time >> to check against the specs to see what the correct format should be. > > I think this syntax is supposed to work according to the SQL spec. > Tom > Lockhart was fooling around with making that stuff spec-compliant > before > he left the project, and no one has bothered to pick it up since :-(. > Perhaps everyone thinks the spec syntax for interval constants is so > bizarre and non-orthogonal it's not worth dealing with ... Well, for what it's worth, I'm interested. I wasn't aware of this particular problem, and I can't say when I'll get around to doing something about it, but now I've at least written it down on my personal todo. Michael Glaesemann grzm seespotcode net