dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found

From: "Tim Lynch" <admin+pgsqladmin(at)thirdage(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: dumpBlobs(): could not open large object: ERROR: inv_open: large object 23312462 not found
Date: 2003-02-19 19:02:19
Message-ID: 05c701c2d849$6d2b6d50$2c0210ac@loisaida
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

version(): PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
redhat 7.3

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

vacuums okay.

is this from deleting large objects without deleting the oid in a table or
vice versa? pgdump exits non-zero which i guess means the backup is
incomplete.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2003-02-19 19:09:44 Re: What is the datetime type equivalent from v7.0.2 to v7.3.1???
Previous Message P G 2003-02-19 18:55:11 How do I upgrade or coexist PostgreSQL on a Cobalt XTR system?