Message-ID: <4A2F2923.2010304@cheapcomplexdevices.com>
Date: Tue, 09 Jun 2009 20:31:47 -0700
From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Ron Mayer <rm_pg@cheapcomplexdevices.com>, Sebastien FLAESCH <sf@4js.com>,
	pgsql-general@postgresql.org, mmoncure@gmail.com
Subject: Re: INTERVAL SECOND limited to 59 seconds?
References: <4A127038.3010103@4js.com>
	<4A2C0E02.9070908@cheapcomplexdevices.com>
	<17203.1244402910@sss.pgh.pa.us>
	<4A2DABF5.3070906@cheapcomplexdevices.com>
	<208.1244587299@sss.pgh.pa.us> <1256.1244588367@sss.pgh.pa.us>
	<4A2F1F3B.1080308@cheapcomplexdevices.com>
	<5401.1244602759@sss.pgh.pa.us>
In-Reply-To: <5401.1244602759@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> Ron Mayer <rm_pg@cheapcomplexdevices.com> writes:
>>     regression=# select interval '1 1' hour;
> 
> Hmm, not sure about that one.  We decided a week or two back that we
> don't want the thing discarding higher-order field values, and this
> seems pretty close to that.  As the code is set up (plus my patch)
> I think it's the case that only the rightmost field specification
> of the interval qualifier makes any difference for parsing the value;
> the leftmost field doesn't really affect what we think the constant
> means.  That seems like a nice simple consistency property ...

Sounds good.  I'm happy with it then.