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