Re: date out of range for timestamp

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rericha <d(dot)rericha(at)healthcareoss(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: date out of range for timestamp
Date: 2010-12-29 02:45:48
Message-ID: 23542.1293590748@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

[ please keep the list cc'd ]

David Rericha <d(dot)rericha(at)healthcareoss(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David Rericha 2010-12-29 03:01:51 Re: date out of range for timestamp
Previous Message Tom Lane 2010-12-29 01:36:20 Re: date out of range for timestamp