| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Vasiliy I Ozerov <vozerov(at)2reallife(dot)com> | 
| Cc: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: Unexpected chunk size when doing dump | 
| Date: | 2013-02-07 15:41:11 | 
| Message-ID: | 12393.1360251671@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
Vasiliy I Ozerov <vozerov(at)2reallife(dot)com> writes:
> I have an error, when doing database dump:
> pg_dump: [archiver (db)] query failed: ERROR: unexpected chunk size 384 (expected 389) in final chunk 1 for toast value 11589 in pg_toast_2619
That looks like a data corruption problem :-(.  You might want to check
into whether your disks/filesystems are properly configured to honor
fsync.
Assuming this is the only problem, you're in luck as far as recovery
goes, because pg_toast_2619 is the toast table for pg_statistic, which
means there's no irreplaceable data in there.  I'd suggest truncating
pg_statistic (as superuser) and then doing a database-wide ANALYZE to
rebuild the content.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Milos Gajdos | 2013-02-07 18:16:41 | Postgres 9.1 statistics in pg_stat_database | 
| Previous Message | Jaime Casanova | 2013-02-07 14:58:49 | Re: Postgres en Cluster |