pg_dump: dumpBlobs(): could not open large object: ERROR: large object 27729547 does not exist - Mailing list pgsql-general

From Manoj Agarwal
Subject pg_dump: dumpBlobs(): could not open large object: ERROR: large object 27729547 does not exist
Date
Msg-id 000a01cf1908$d9a97d30$8cfc7790$@be
Whole thread Raw
Responses Re: pg_dump: dumpBlobs(): could not open large object: ERROR: large object 27729547 does not exist
Re: pg_dump: dumpBlobs(): could not open large object: ERROR: large object 27729547 does not exist
List pgsql-general

Hi,

 

I have a Postgresql-7.4.19  database in SQL_ASCII Encoding format.  There is a table, besides other tables, in the database, that is used to store BLOBs through a Web-based application.  I normally take database backup using pg_dump, as and when needed, and it has always worked fine.  It was needed as a special case to manually delete some of the records for BLOBs directly from the back-end.  I took backup of the database using pg_dump before deleting the records.  Then, I deleted the required records via psql prompt from that table.  Then, I tried another database backup using pg_dump, but it gave error: “pg_dump: dumpBlobs(): could not open large object: ERROR:  large object 27729547 does not exist.”  I have been looking into PostgreSQL forums for this issue, and it is suggested that ‘pg_largeobject’ table might contain invalid references towards blobs, and REINDEX table pg_largeobject should fix the issue.  Is this the only possible solution in this case or some other solution also exists?  Also, when this REINDEX is done by Postgres? Is it needed to be done manually or we can force it automatically somehow?  What are the chances of REINDEX operation goes wrong/bust?

 

Please suggest.

 

Kind Regards,

Manoj Agarwal

pgsql-general by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: Help with details of what happens when I create a constraint NOT VALID
Next
From: Emmanuel Medernach
Date:
Subject: postgres-fdw questions