Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 40C0464FCD2 for ; Thu, 11 Sep 2008 19:49:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 37171-03 for ; Thu, 11 Sep 2008 19:48:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp103.biz.mail.mud.yahoo.com (smtp103.biz.mail.mud.yahoo.com [68.142.200.238]) by postgresql.org (Postfix) with SMTP id 67AF264FCBD for ; Thu, 11 Sep 2008 19:48:57 -0300 (ADT) Received: (qmail 65839 invoked from network); 11 Sep 2008 22:48:55 -0000 Received: from unknown (HELO ?192.168.5.105?) (ramayer@forensiclogic.com@75.36.176.183 with plain) by smtp103.biz.mail.mud.yahoo.com with SMTP; 11 Sep 2008 22:48:55 -0000 X-YMail-OSG: 0My.jUcVM1nQJjvYIBeCCpecSSQfSvAH7JlPrnaa0lqEnC9XP58I2R_W3zreLU32gir8H11MjO3rPdzR564sEqyMlXi2gAjnoBiSAoBaZtZtZl_eZGeRm.p9HuwWxvt482bs3VVH4pqsLxf7q6MyDKSo X-Yahoo-Newman-Property: ymail-3 Message-ID: <48C9A056.4010205@cheapcomplexdevices.com> Date: Thu, 11 Sep 2008 15:48:54 -0700 From: Ron Mayer User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Tom Lane , Ron Mayer CC: Robert Treat , pgsql-general@postgresql.org, Amber , Andrew Sullivan , simon@2ndQuadrant.com Subject: Re: PostgreSQL TPC-H test result? References: <20080909123947.GA59092@commandprompt.com> <200809091129.54467.robert@omniti.com> <24765.1220992015@sss.pgh.pa.us> In-Reply-To: <24765.1220992015@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/524 X-Sequence-Number: 137531 Tom Lane wrote: >> interval '1' year. > > ...is SQL spec syntax, but it's not fully implemented in Postgres... > > Or someone could try to make it work, but given that no one has taken > the slightest interest since Tom Lockhart left the project, I wouldn't > hold my breath waiting for that. I have interest. For 5 years I've been maintaining a patch for a client that allows the input of ISO-8601 intervals (like 'P1YT1M') rather than the nonstandard shorthand ('1Y1M') that postgresql supports[1]. I'd be interested in working on this. Especially if supporting SQL standard interval syntax could improve the chances of getting my ISO-8601-interval-syntax replacing nonstandard-postgres-shorthand-intervals patch accepted again, I'd be quite happy work on it. Tom in 2003 said my code looked cleaner than the current code[2], and the patch was accepted[3] for a while before being rejected - I believe because Peter said he'd like to see the SQL standard intervals first. I see it's still a TODO, though. > the grammar supports it but the info doesn't get propagated to > interval_in, and interval_in wouldn't know what to do even if it did > have the information that there was a YEAR qualifier after the literal. Any hints on how best to propagate the needed info from the grammar? Or should it be obvious to me from reading the code? [1] http://archives.postgresql.org/pgsql-patches/2003-09/msg00119.php [2] http://archives.postgresql.org/pgsql-patches/2003-09/msg00121.php [3] http://archives.postgresql.org/pgsql-patches/2003-12/msg00253.php Ron Mayer (formerly ron@intervideo.com who posted those ISO-8601 interval patches)