pg_dump: dumpBlobs(): could not open large object: ERROR: large object 27729547 does not exist
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
Manoj Agarwal <ma@ockham.be> wrote:
I have a Postgresql-7.4.19 database
Did you mean 8.4.19 or are you really running on a release which
has been out of support since 2010?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Fri, Jan 24, 2014 at 10:33 PM, Manoj Agarwal <ma@ockham.be> wrote:
Hi,
I have a Postgresql-7.4.19 database in SQL_ASCII Encoding format.
You should really consider an upgrade first... As mentioned by Kevin
this version is outdated. The latest versions of pg_dump support
servers down to 7.4 so an upgrade is doable.
Regards,
--
Michael
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On 26 Jan 2014, at 2:34, Michael Paquier <michael.paquier@gmail.com> wrote:
On Fri, Jan 24, 2014 at 10:33 PM, Manoj Agarwal <ma@ockham.be> wrote:
Hi,
I have a Postgresql-7.4.19 database in SQL_ASCII Encoding format.
You should really consider an upgrade first... As mentioned by Kevin
this version is outdated. The latest versions of pg_dump support
servers down to 7.4 so an upgrade is doable.
That raises an interesting question: How far back will support for older versions in pg_dump go?
I assume at some point it will no longer be feasible for pg_dump to still support PG 7.4 and support will be dropped. At that point, if you’re still running on such an old version of the database server, not only will you be out of support (for a long time already), but your upgrade path will be barred.
Of course, you could then do an intermediary upgrade to an older version than what’s current that still supports dumping from the version of the database that you’re on, but at some point you will find it difficult to obtain those versions as well.
Would it help to put such bottom line version numbers on the Postgres site as a warning, so that people have a number to verify that they never ever should get below, no matter what? Perhaps the lowest version supported by pg_dump could be added as a column to the EOL dates or something?
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Alban Hertroys <haramrae@gmail.com> wrote:
That raises an interesting question: How far back will support
for older versions in pg_dump go?
http://www.postgresql.org/docs/current/interactive/app-pgdump.html#PG-DUMP-NOTES
says:
| pg_dump can also dump from PostgreSQL servers older than its own
| version. (Currently, servers back to version 7.0 are supported.)
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Kevin Grittner <kgrittn@ymail.com> writes:
Alban Hertroys <haramrae@gmail.com> wrote:
That raises an interesting question: How far back will support
for older versions in pg_dump go?
http://www.postgresql.org/docs/current/interactive/app-pgdump.html#PG-DUMP-NOTES
says:
| pg_dump can also dump from PostgreSQL servers older than its own
| version. (Currently, servers back to version 7.0 are supported.)
There's been talk of dropping pg_dump's support for dumping from pre-7.3
servers, as that would allow removing quite a lot of crufty and no longer
well-tested code. (7.3 is an interesting cutoff because that release
introduced both schema support and pg_depend dependency tracking.)
Not sure when we will get around to that, but it seems likely to happen at
some point.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general