Re: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Tim Lynch" <admin+pgsqladmin(at)thirdage(dot)com>
- Cc: pgsql-admin(at)postgresql(dot)org
- Subject: Re: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found
- Date: Wed, 19 Feb 2003 22:57:24 -0500
- Message-id: <16939.1045713444@sss.pgh.pa.us> <text/plain>
"Tim Lynch" <admin+pgsqladmin(at)thirdage(dot)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
Home |
Main Index |
Thread Index