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

Interesting.. I was able to pg_restore -f to a file... and then psql -f  the
resulting file. and it loaded just fine.. the down side to this method is I
cannot use the parallel load function (and the extra time). but I am glad
that I got the data loaded. Let me know if there is any other info I get
you.

On Thu, Jul 21, 2011 at 12:58 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Greg Johnson <greg.johnson@interprose.com> writes:
> > On Thu, Jul 21, 2011 at 11:44 AM, Tom Lane <tgl@sss.pgh.pa.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
>



--
----------------------------------------------------------------
Greg Johnson
The InterProse Corporation
Software Developer
Phone: (360) 604-3531 x225
Fax: (360) 604-3579