Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1D44D9FBEB2 for ; Thu, 22 Feb 2007 11:43:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 08052-02-6 for ; Thu, 22 Feb 2007 11:43:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 9FD5D9FBE88 for ; Thu, 22 Feb 2007 11:43:45 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l1MFhXea005459; Thu, 22 Feb 2007 10:43:33 -0500 (EST) To: mailreg@numerixtechnology.de cc: pgsql-sql@postgresql.org Subject: Re: pg_dump fails (timestamp out of range) In-reply-to: <45DD82AC.2030800@numerixtechnology.de> References: <45DD82AC.2030800@numerixtechnology.de> Comments: In-reply-to T E Schmitz message dated "Thu, 22 Feb 2007 11:46:52 +0000" Date: Thu, 22 Feb 2007 10:43:33 -0500 Message-ID: <5458.1172159013@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.06 tagged_above=0 required=5 tests=AWL, BAYES_50, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200702/226 X-Sequence-Number: 27560 T E Schmitz writes: > However, I am stalled because pg_dump fails with the following error: > pg_dump: ERROR: timestamp out of range > pg_dump: SQL command to dump the contents of table "server_hit_bin" > failed: PQendcopy() failed. You should treat this as a corrupt-data exercise: you need to identify and fix (or delete) the offending row(s). In this case you might try tests like "bin_end_date_time > '1 Jan 9999'" and so on to see if you can determine exactly which rows are bad. regards, tom lane