| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> | 
| Cc: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: pg_dump: Error message from server: ERROR: compressed data is corrupt | 
| Date: | 2010-04-23 14:05:46 | 
| Message-ID: | 7928.1272031546@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-04-23 17:15:15 | Re: Very Dangerous bug in XA connection pooling and SL EJBs with jboss-4.2.3 & latest postgresql-8.4-701.jdbc3.jar | 
| Previous Message | Achilleas Mantzios | 2010-04-23 11:54:42 | pg_dump: Error message from server: ERROR: compressed data is corrupt |