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 03:01:51 |
Message-ID: | 4D1AA49F.8060706@healthcareoss.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(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
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-12-29 03:06:13 | Re: date out of range for timestamp |
Previous Message | Tom Lane | 2010-12-29 02:45:48 | Re: date out of range for timestamp |