From: | David Rericha <d(dot)rericha(at)healthcareoss(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: date out of range for timestamp |
Date: | 2010-12-29 17:11:39 |
Message-ID: | 4D1B6BCB.9040600@healthcareoss.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(dot)rericha(at)healthcareoss(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | nextage Tech | 2010-12-30 07:55:48 | PostgreSQL |
Previous Message | Achilleas Mantzios | 2010-12-29 14:06:41 | SET SESSION AUTHORIZATION and log file entries |