From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vasiliy I Ozerov <vozerov@2reallife.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Unexpected chunk size when doing dump
Date: Thu, 07 Feb 2013 10:41:11 -0500
Message-ID: <12393.1360251671@sss.pgh.pa.us> (raw)
In-Reply-To: <C35C014AFB644AFD8D3254767791FE0E@2reallife.com>
References: <C35C014AFB644AFD8D3254767791FE0E@2reallife.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, vozerov@2reallife.com
Subject: Re: Unexpected chunk size when doing dump
In-Reply-To: <12393.1360251671@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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