From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rericha <d.rericha@healthcareoss.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: date out of range for timestamp
Date: Tue, 28 Dec 2010 22:06:13 -0500
Message-ID: <23839.1293591973@sss.pgh.pa.us> (raw)
In-Reply-To: <4D1AA49F.8060706@healthcareoss.com>
References: <4D1A7AB3.4010008@healthcareoss.com>
<13702.1293586580@sss.pgh.pa.us>
<4D1A9D8E.70803@healthcareoss.com>
<23542.1293590748@sss.pgh.pa.us>
<4D1AA49F.8060706@healthcareoss.com>
David Rericha <d.rericha@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
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: tgl@sss.pgh.pa.us, d.rericha@healthcareoss.com
Subject: Re: date out of range for timestamp
In-Reply-To: <23839.1293591973@sss.pgh.pa.us>
* 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