Thread: Can't import large objects in most recent cvs (20020531 -- approx 1pm PDT)

I'm trying to determine if database growth (with LO) that I'm seeing during
a pg_restore is fixed by the patch identified at
http://archives.postgresql.org/pgsql-hackers/2002-04/msg00496.php , but when
I attempt to restore from a 7.2.1 created dump into my newly created
7.3devel database, I get this:

pg_restore: [archiver (db)] could not create large object cross-reference
table:

I didn't find any mention of this on the hackers mail archive, so I thought
I'd pass it on.

The dump file was created with:
pg_dump --blobs --format=c --quotes --oids --compress=5 quickview >
quickview.dump

and restored with:
pg_restore -d quickview < quickview.dump
(although I don't think either of those are the problem, because we've used
those command lines successfully with 7.2 and 7.2.1 w/o problems).

If nobody else is having this problem I'll see if I can create a small test
case. (my dump file is 10 gigs)

-ron

Ron Snyder <snyder@roguewave.com> writes:
> I attempt to restore from a 7.2.1 created dump into my newly created
> 7.3devel database, I get this:

> pg_restore: [archiver (db)] could not create large object cross-reference
> table:

> I didn't find any mention of this on the hackers mail archive, so I thought
> I'd pass it on.

News to me; and I just tested that code a couple days ago after hacking
on it for schema support.  Would you look in the postmaster log to see
exactly what error message the backend is issuing?  Might help to run
pg_restore with "PGOPTIONS=--debug_print_query=1" so you can verify the
exact query that's failing, too.

(I've thought several times that we should clean up pg_dump and
pg_restore so that they report the failed query and backend message in
*all* cases; right now they're pretty haphazard about it.)
        regards, tom lane