Message-ID: <4D1AA49F.8060706@healthcareoss.com>
Date: Tue, 28 Dec 2010 21:01:51 -0600
From: David Rericha <d.rericha@healthcareoss.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.15) Gecko/20101026 SUSE/3.0.10 Thunderbird/3.0.10
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: pgsql-admin@postgresql.org
Subject: Re: date out of range for timestamp
References: <4D1A7AB3.4010008@healthcareoss.com>
	<13702.1293586580@sss.pgh.pa.us> <4D1A9D8E.70803@healthcareoss.com>
	<23542.1293590748@sss.pgh.pa.us>
In-Reply-To: <23542.1293590748@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks, Tom.  That was it.  After I ran analyze on the table, the error
disappeared.

David J. Rericha
OSS, LLC
Projects Manager
563-650-5446


On 12/28/2010 08:45 PM, Tom Lane wrote:
> [ please keep the list cc'd ]
>
> David Rericha <d.rericha@healthcareoss.com> writes:
>   
>> I am truly typing the date as a literal.  It turned out that I did have
>> a date of year 2010000, which would have been out of range, but I
>> changed it.  But I still get the error.
>>     
> Hmm.  Try re-running ANALYZE on the table.  I'm thinking that maybe
> (a) the way-out-of-line date is still in the statistical histogram, and
> (b) the planner is using date-to-timestamp coercion while trying to
> estimate the selectivity of the <= condition.
>
> 			regards, tom lane
>
>
>