Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 0158163306D for ; Fri, 23 Apr 2010 11:06:01 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 77909-09 for ; Fri, 23 Apr 2010 14:05:50 +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 6D21A632F70 for ; Fri, 23 Apr 2010 11:05:50 -0300 (ADT) 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 o3NE5kw1007929; Fri, 23 Apr 2010 10:05:46 -0400 (EDT) To: Achilleas Mantzios cc: pgsql-admin@postgresql.org Subject: Re: pg_dump: Error message from server: ERROR: compressed data is corrupt In-reply-to: <201004231454.43104.achill@matrix.gatewaynet.com> References: <201004231454.43104.achill@matrix.gatewaynet.com> Comments: In-reply-to Achilleas Mantzios message dated "Fri, 23 Apr 2010 13:54:42 +0200" Date: Fri, 23 Apr 2010 10:05:46 -0400 Message-ID: <7928.1272031546@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: 201004/316 X-Sequence-Number: 34410 Achilleas Mantzios writes: > Then i did > # CREATE TABLE mail_entity2 AS SELECT * FROM mail_entity; > which went fine > but, for some crazy reason, pg_dump on mail_entity2 also results to an error: > srv:~> pg_dump -t mail_entity2 > /dev/null > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: compressed data is corrupt The create/select would not have bothered to decompress any inline-compressed datums, so the corrupted data went right over to the new table. I think you'll have to engage in another round of divide-and-conquer to locate the specific row or rows with a corrupted value. regards, tom lane