From: David Rericha <d.rericha@healthcareoss.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: date out of range for timestamp
Date: Tue, 28 Dec 2010 21:01:51 -0600
Message-ID: <4D1AA49F.8060706@healthcareoss.com> (raw)
In-Reply-To: <23542.1293590748@sss.pgh.pa.us>
References: <4D1A7AB3.4010008@healthcareoss.com>
<13702.1293586580@sss.pgh.pa.us>
<4D1A9D8E.70803@healthcareoss.com>
<23542.1293590748@sss.pgh.pa.us>
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.rericha@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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: d.rericha@healthcareoss.com, tgl@sss.pgh.pa.us
Subject: Re: date out of range for timestamp
In-Reply-To: <4D1AA49F.8060706@healthcareoss.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox