From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pg_dumpall 8.1.4 large objects error |
Date: | 2006-06-07 01:33:06 |
Message-ID: | Pine.LNX.4.64.0606061826420.23923@discord.home.frostconsultingllc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I'm curious why this would happen:
pg_dump: dumpBlobs(): could not open large object: ERROR: inv_open: large
object 145391 not found
The db being dumped is 7.3.2 and the pg_dumpall is from a source compiled
8.1.4. The OS in question is Redhat 8 (soon to be upgraded). When I used the
7.3.2 pg_dump -b, everything dumped out ok, but using the 8.1.4 pg_dumpall
which is supposed to properly handle large objects, I received this error.
Note, there's only the single error above, and I still ended up with a 17gig
bzipped file. The 7.3.2 pg_dump yielded a 16gig file in custom format with
default compression.
I need to get a reasonable dump so I can upgrade this ancient system. Should
I upgrade to the most recent 7.3.x version before doing the dump to have the
most reasonable chance of success?
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-07 03:16:56 | Re: pg_dumpall 8.1.4 large objects error |
Previous Message | Jim C. Nasby | 2006-06-06 21:58:32 | Re: oralink documentation |