Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 9DE301337999 for ; Tue, 28 Dec 2010 23:06:25 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 57126-04-2 for ; Wed, 29 Dec 2010 03:06:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 85FB21337B9B for ; Tue, 28 Dec 2010 23:06:15 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oBT36Ddr023840; Tue, 28 Dec 2010 22:06:13 -0500 (EST) To: David Rericha cc: pgsql-admin@postgresql.org Subject: Re: date out of range for timestamp 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> Comments: In-reply-to David Rericha message dated "Tue, 28 Dec 2010 21:01:51 -0600" Date: Tue, 28 Dec 2010 22:06:13 -0500 Message-ID: <23839.1293591973@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/201 X-Sequence-Number: 36430 David Rericha 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