Re: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found - Mailing list pgsql-admin

From Tom Lane
Subject Re: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found
Date
Msg-id 16939.1045713444@sss.pgh.pa.us
Whole thread Raw
In response to dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found  ("Tim Lynch" <admin+pgsqladmin@thirdage.com>)
List pgsql-admin
"Tim Lynch" <admin+pgsqladmin@thirdage.com> writes:
> i've made a backup script, the meat and potatos of which are:
> /usr/bin/pg_dump -Fc --blobs -f $dumpdir/$file $dbname
> had been working, but recently:
>  pg_dump: dumpBlobs(): could not open large object: ERROR:  inv_open: large
> object 23312462 not found

> for a variety of oids, not NULL or oid 0; over the last few days: 23170697
> 23208208 23240773 23312462 23318306 23356032 23356728 23495969 23554296
> 23578064

After looking at the code, the most plausible explanation seems to be
that the index on pg_largeobject is broken.  Try reindexing
pg_largeobject.  (You'l likely need to do this in single-user mode;
read the REINDEX man page carefully.)

7.2.1 is by no means current, btw.  I recommend an update to 7.2.4 at
least, or 7.3 if you can.

            regards, tom lane

pgsql-admin by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: How to avoid the Mutating Triggers ??
Next
From: "Donald Fraser"
Date:
Subject: Re: pg_dumpall