pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Unexpected chunk size when doing dump 2+ messages / 2 participants [nested] [flat]
* Unexpected chunk size when doing dump @ 2013-02-07 13:02 Vasiliy I Ozerov <vozerov@2reallife.com> 2013-02-07 15:41 ` Re: Unexpected chunk size when doing dump Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Vasiliy I Ozerov @ 2013-02-07 13:02 UTC (permalink / raw) To: pgsql-admin Good day! I have an error, when doing database dump: psql -U postgres -p 56432 postgres > postgres.sql 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 pg_dump: [archiver (db)] query was: SELECT description, classoid, objoid, objsubid FROM pg_catalog.pg_description ORDER BY classoid, objoid, objsubid Postgresql version is 9.0. There was not any problems with hard drives. The same error I get, when I am trying to dump db at slave server (replic). Reindex doesn't help me :( What can I do with this error? Thank you! -- Vasiliy I Ozerov ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Unexpected chunk size when doing dump 2013-02-07 13:02 Unexpected chunk size when doing dump Vasiliy I Ozerov <vozerov@2reallife.com> @ 2013-02-07 15:41 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2013-02-07 15:41 UTC (permalink / raw) To: Vasiliy I Ozerov <vozerov@2reallife.com>; +Cc: pgsql-admin Vasiliy I Ozerov <vozerov@2reallife.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 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2013-02-07 15:41 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2013-02-07 13:02 Unexpected chunk size when doing dump Vasiliy I Ozerov <vozerov@2reallife.com> 2013-02-07 15:41 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox