pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Glaesemann <grzm@seespotcode.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: Cronje Fourie <cfourie@e-intelligence.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: TPCH Benchmark query result invalid
Date: Wed, 13 Dec 2006 14:13:34 +0900
Message-ID: <E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net> (raw)
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>


On Dec 13, 2006, at 1:23 , Tom Lane wrote:

> Richard Huxton <dev@archonet.com> 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





view thread (5+ messages)  latest in thread

Message-ID: <E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net>
Permalink:  ../E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net/
Also on:    postgresql.org/message-id/E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: grzm@seespotcode.net, tgl@sss.pgh.pa.us, dev@archonet.com, cfourie@e-intelligence.com
  Subject: Re: TPCH Benchmark query result invalid
  In-Reply-To: <E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox