Re: error restoring large objects during pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Snyder <snyder(at)roguewave(dot)com>
Cc: "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>
Subject: Re: error restoring large objects during pg_restore
Date: 2003-06-10 23:03:50
Message-ID: 6225.1055286230@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Snyder <snyder(at)roguewave(dot)com> writes:
> I'm trying to pg_restore a database using a process that I've used a bunch
> (10-15) times in the past, and this is the first time it's ever failed on
> me. It's failing with the following error:

> pg_restore: creating table for large object cross-references
> pg_restore: [custom archiver] could not read data block - expected 1, got 0
> pg_restore: *** aborted because of error

Hm. Looking at the code, this appears to be an unexpected-EOF kind of
error (it expected to be able to read 1 more byte of data, and there
wasn't any).

> Jun 10 14:24:19 vault pgqv[16995]: [242528] DEBUG: query: Insert Into
> dump_blob_xref(oldOid, newOid) Values (1, 60983759);

> I've done this twice, with two different db dumps, and both have given me
> the same error. I'm wondering if that last line (with the oldOid value of
> 1) is significant.

I think the "1" is coincidental. It does seem that there is something
broken about the format of the dump file though. What version pg_dump
were you using, exactly?

Other things to check would include accidental truncation or corruption
of the dump file (eg, copying it onto a Windows machine might result in
newline conversion, which would be bad).

Philip, any other ideas where to look?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2003-06-10 23:24:04 Some OLAP open source project out there?
Previous Message Dmitry Tkach 2003-06-10 23:01:41 Re: referential integrity violations