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.reri...@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 > > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
