From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dump: Error message from server: ERROR: compressed data is corrupt |
Date: | 2010-04-27 12:52:27 |
Message-ID: | 201004271552.28147.achill@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Στις Friday 23 April 2010 17:05:46 ο/η Tom Lane έγραψε:
> Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> 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.
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 rather than
actual corrupted data on the disk.
I have a decent dump now,
thank you a lot.
>
> regards, tom lane
>
--
Achilleas Mantzios
From | Date | Subject | |
---|---|---|---|
Next Message | M.Nasir Aftab | 2010-04-28 06:49:32 | Information required |
Previous Message | Julius Tuskenis | 2010-04-27 06:01:16 | Re: when does postgresql read from pg_hba.conf ?? |