Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Johnson <greg(dot)johnson(at)interprose(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin
Date: 2011-07-21 19:58:29
Message-ID: 19302.1311278309@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greg Johnson <greg(dot)johnson(at)interprose(dot)com> writes:
> On Thu, Jul 21, 2011 at 11:44 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This looks like pg_restore is terminating unexpectedly. What do you see
>> on the client end of it?

> pg_restore: [custom archiver] could not read from input file: end of file

Well, that suggests you have a truncated or otherwise corrupted pg_dump
archive file. Do you get a similar failure if you just do "pg_restore
-l" on the archive file? Is the pg_dump run reporting any signs of
distress?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Johnson 2011-07-21 20:29:42 Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin
Previous Message Greg Johnson 2011-07-21 19:00:35 Re: BUG #6127: pg_restore failing: unexpected message type 0x58 during COPY from stdin