X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id F0B0D9FA3A6 for ; Wed, 7 Jun 2006 00:17:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 55570-02 for ; Wed, 7 Jun 2006 00:17:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id BCE169FA0E5 for ; Wed, 7 Jun 2006 00:17:00 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k573Guu6025293; Tue, 6 Jun 2006 23:16:56 -0400 (EDT) To: Jeff Frost cc: pgsql-admin@postgresql.org Subject: Re: pg_dumpall 8.1.4 large objects error In-reply-to: References: Comments: In-reply-to Jeff Frost message dated "Tue, 06 Jun 2006 18:33:06 -0700" Date: Tue, 06 Jun 2006 23:16:56 -0400 Message-ID: <25292.1149650216@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/41 X-Sequence-Number: 22003 Jeff Frost writes: > I'm curious why this would happen: > pg_dump: dumpBlobs(): could not open large object: ERROR: inv_open: large > object 145391 not found Some cursory trawling in the REL7_3 sources says that this means that "SELECT DISTINCT loid FROM pg_largeobject" found a large object OID that then could not be found by an indexscan of pg_largeobject. So I'd try a REINDEX of pg_largeobject to see if that fixes it. See the REINDEX man page concerning hoops you have to jump through to reindex a system catalog --- IIRC, the hoops are much higher and narrower back in 7.3. > The db being dumped is 7.3.2 Of course, I'm reading 7.3.15 sources ... regards, tom lane