From: David Rericha <d.rericha@healthcareoss.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: date out of range for timestamp
Date: Wed, 29 Dec 2010 11:11:39 -0600
Message-ID: <4D1B6BCB.9040600@healthcareoss.com> (raw)
In-Reply-To: <23839.1293591973@sss.pgh.pa.us>
References: <4D1A7AB3.4010008@healthcareoss.com>
<13702.1293586580@sss.pgh.pa.us>
<4D1A9D8E.70803@healthcareoss.com>
<23542.1293590748@sss.pgh.pa.us>
<4D1AA49F.8060706@healthcareoss.com>
<23839.1293591973@sss.pgh.pa.us>
Tom, it seems to me that the planner's behavior in converting dates to
timestamps in order to compare a date constant is a bug. I think I will
submit it as such. If you enter a valid date into a field, you should
be able to filter it even if that date exceeds the timestamp's range.
Thanks again for your help.
David J. Rericha
OSS, LLC
Projects Manager
563-650-5446
On 12/28/2010 09:06 PM, Tom Lane wrote:
> David Rericha <d.rericha@healthcareoss.com> writes:
>
>> Thanks, Tom. That was it. After I ran analyze on the table, the error
>> disappeared.
>>
> Yeah, I just duplicated the failure here. It only happens if the
> comparison value falls into the histogram bucket adjoining the
> out-of-range value, which is why you didn't see it happen for some
> values of the comparison constant. Doesn't look too hard to fix.
>
> regards, tom lane
>
>
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-admin@postgresql.org
Cc: d.rericha@healthcareoss.com, tgl@sss.pgh.pa.us
Subject: Re: date out of range for timestamp
In-Reply-To: <4D1B6BCB.9040600@healthcareoss.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