Re: error restoring large objects during pg_restore (re

The resolution for this turned out to be going back to a dump from a week
ago.  As near as we can ascertain, we had been getting corrupted dumps and
hadn't been paying enough attention to the output of the command.

This output from our cronjob:
pg_dump: dumpBlobs(): could not open large object: ERROR:  inv_open: large
object 57615414 not found

It's not clear to us why we are/were having this problem during a pg_dump,
but we think that the error messages here caused the dump to be no good.
Any ideas what could cause this error during the dump?  I'm hoping to get
everything moved up to 7.3.3 (from 7.2.1) soon, and see if we still get the
error.

-ron



> -----Original Message-----
> From: Ron Snyder [mailto:snyder@roguewave.com]
> Sent: Tuesday, June 10, 2003 8:51 PM
> To: 'Tom Lane'
> Cc: 'pgsql-general@postgresql.org'; 'Philip Warner'
> Subject: Re: [GENERAL] error restoring large objects during
> pg_restore
>
>
> Oh yeah, I forgot to mention that the partition the dumps are
> being written
> to are large enough to hold 5 times as much data as they've
> got.  These
> dumps are the only thing of any consequence (size) that are
> being written to
> the partition, so the dumps aren't being truncated by out of
> disk space
> problems.
>
> -ron
>
> > -----Original Message-----
> > From: Ron Snyder
> > Sent: Tuesday, June 10, 2003 4:52 PM
> > To: 'Tom Lane'; Ron Snyder
> > Cc: 'pgsql-general@postgresql.org'; Philip Warner
> > Subject: RE: [GENERAL] error restoring large objects during
> > pg_restore
> >
> >
> > This is with postgresql 7.2.1 (we're in the process of moving
> > to 7.3.3).  I believe that the chance of file corruption
> > should be very low-- Windows boxes have no opportunity to
> > touch this file. The server is a RH Linux box with logical
> > volumes (both as storage for the dump files and the storage
> > for the database).
> >
> > Thanks for looking!
> >
> > I'm currently "strace"ing the pg_restore to see if that lends
> > any clues.
> >
> > -ron
> >
> > > -----Original Message-----
> > > From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> > > Sent: Tuesday, June 10, 2003 4:04 PM
> > > To: Ron Snyder
> > > Cc: 'pgsql-general@postgresql.org'; Philip Warner
> > > Subject: Re: [GENERAL] error restoring large objects during
> > > pg_restore
> > >
> > >
> > > Ron Snyder <snyder@roguewave.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
> > >
> >
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>