Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 49A4F9FB35A for ; Mon, 26 Feb 2007 07:05:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 46512-04 for ; Mon, 26 Feb 2007 07:05:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from zebedee.cranntara.net (zebedee.cranntara.net [91.186.7.79]) by postgresql.org (Postfix) with ESMTP id 501D39FB34E for ; Mon, 26 Feb 2007 07:05:24 -0400 (AST) Received: from dial-dynamic-62-69-36-171.surfdial.murphx.net ([62.69.36.171] helo=bolek.coachhouse) by zebedee.cranntara.net with esmtpsa (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.62) (envelope-from ) id 1HLdfT-0000bt-1I; Mon, 26 Feb 2007 11:05:20 +0000 Received: from [192.168.0.32] (helo=[192.168.0.32]) by bolek.coachhouse with esmtp (Exim 4.50) id 1HLdfI-00044Q-TT; Mon, 26 Feb 2007 11:05:08 +0000 Message-ID: <45E2BEE4.5090003@numerixtechnology.de> Date: Mon, 26 Feb 2007 11:05:08 +0000 From: T E Schmitz Reply-To: mailreg@numerixtechnology.de User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgresql.org Subject: Re: pg_dump fails (timestamp out of range) References: <45DD82AC.2030800@numerixtechnology.de> <5458.1172159013@sss.pgh.pa.us> In-Reply-To: <5458.1172159013@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.186 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200702/262 X-Sequence-Number: 27596 Tom Lane wrote: > T E Schmitz writes: > >>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. Dear Tom, I can't thank you enough for the above advice. The test above identified 3 records and once they were removed I was able to dump the DB. -- Best Regards, Tarlika Elisabeth Schmitz