From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Organization: Dynacom Tankers Mgmt
To: pgsql-admin@postgresql.org
Subject: Re: pg_dump: Error message from server: ERROR: compressed data is
	corrupt
Date: Tue, 27 Apr 2010 14:52:27 +0200
User-Agent: KMail/1.9.7
References: <201004231454.43104.achill@matrix.gatewaynet.com>
	<7928.1272031546@sss.pgh.pa.us>
In-Reply-To: <7928.1272031546@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <201004271552.28147.achill@matrix.gatewaynet.com>

=CE=A3=CF=84=CE=B9=CF=82 Friday 23 April 2010 17:05:46 =CE=BF/=CE=B7 Tom La=
ne =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:
> Achilleas Mantzios <achill@matrix.gatewaynet.com> writes:
> > Then i did
>=20
> > # CREATE TABLE mail_entity2 AS SELECT * FROM mail_entity;
>=20
> > which went fine
>=20
> > 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
>=20
> 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.

We just removed one memory SIM, and the problem went away.
It must have been a problem caused by on the fly memory hardware error rath=
er than
actual corrupted data on the disk.
I have a decent dump now,
thank you a lot.

>=20
> 			regards, tom lane
>=20


=2D-=20
Achilleas Mantzios