Re: failures in pg_restore -- possibly corrupt archive

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: AccessDevelopment TEST <caleb(dot)access(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: failures in pg_restore -- possibly corrupt archive
Date: 2014-01-02 22:31:40
Message-ID: 18119.1388701900@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

AccessDevelopment TEST <caleb(dot)access(at)gmail(dot)com> writes:
> I am attempting to restore a pg dump file and am getting this error message:
> pg_restore: [custom archiver] could not find block ID 229750 in archive
> -- possibly corrupt archive
> pg_restore: [custom archiver] could not find block ID 228874 in archive
> -- possibly corrupt archive
> pg_restore: [archiver] worker process failed: exit code 1

> The pg_restore command used is:
> pg_restore -j 12 -d mydb -h myhost -U username /restore/file.dump

This looks suspiciously like some old complaints about unsupported cases
in parallel restore. Does it work if you omit the -j option? If so,
what versions of pg_dump and pg_restore are you using exactly, and what
did the pg_dump command look like?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Caleb Access 2014-01-02 22:55:10 failures in pg_restore -- possibly corrupt archive
Previous Message AccessDevelopment TEST 2014-01-02 22:03:23 failures in pg_restore -- possibly corrupt archive