pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: Robert Treat <robert@omniti.com>
Cc: pgsql-general@postgresql.org, Amber <guxiaobo1982@hotmail.com>
Cc: Andrew Sullivan <ajs@commandprompt.com>
Cc: simon@2ndQuadrant.com
Subject: Re: PostgreSQL TPC-H test result?
Date: Thu, 11 Sep 2008 15:48:54 -0700
Message-ID: <48C9A056.4010205@cheapcomplexdevices.com> (raw)
In-Reply-To: <24765.1220992015@sss.pgh.pa.us>
References: <BLU139-DS5AB90A6E11E3F439F0006CD540@phx.gbl>
	<20080909123947.GA59092@commandprompt.com>
	<BLU139-DS28D9D90A25BD2AD8CDEF0CD540@phx.gbl>
	<200809091129.54467.robert@omniti.com>
	<24765.1220992015@sss.pgh.pa.us>

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)




view thread (17+ messages)  latest in thread

Message-ID: <48C9A056.4010205@cheapcomplexdevices.com>
Permalink:  ../48C9A056.4010205@cheapcomplexdevices.com/
Also on:    postgresql.org/message-id/48C9A056.4010205@cheapcomplexdevices.com

 · 

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-performance@postgresql.org
  Cc: rm_pg@cheapcomplexdevices.com, tgl@sss.pgh.pa.us, robert@omniti.com, guxiaobo1982@hotmail.com, ajs@commandprompt.com, simon@2ndQuadrant.com
  Subject: Re: PostgreSQL TPC-H test result?
  In-Reply-To: <48C9A056.4010205@cheapcomplexdevices.com>

* 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