Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 88D919FA2B9 for ; Wed, 1 Nov 2006 19:33:52 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 86642-01 for ; Wed, 1 Nov 2006 23:33:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from macfarlane.asap.unimelb.edu.au (macfarlane.asap.unimelb.edu.au [203.14.107.65]) by postgresql.org (Postfix) with ESMTP id 423DA9F935B for ; Wed, 1 Nov 2006 19:33:49 -0400 (AST) Received: by macfarlane.asap.unimelb.edu.au (Postfix, from userid 1021) id 7AB8E12AEE9; Thu, 2 Nov 2006 10:18:00 +1100 (EST) Received: from [203.14.107.27] (iapetus.asap.unimelb.edu.au [203.14.107.27]) by macfarlane.asap.unimelb.edu.au (Postfix) with ESMTP id 08F7612AEF8; Thu, 2 Nov 2006 10:17:50 +1100 (EST) Message-ID: <45492EE1.2080706@austehc.unimelb.edu.au> Date: Thu, 02 Nov 2006 10:33:53 +1100 From: Peter Neish User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: pg_dump: schema with OID xxxxxxxx does not exist References: <45418477.2020400@austehc.unimelb.edu.au> <6801.1161967193@sss.pgh.pa.us> <45455FA3.2080706@austehc.unimelb.edu.au> <3550.1162174753@sss.pgh.pa.us> <454562F6.7020501@austehc.unimelb.edu.au> <3708.1162176279@sss.pgh.pa.us> In-Reply-To: <3708.1162176279@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.131 tagged_above=0 required=5 tests=SUBJECT_NOVOWEL X-Spam-Level: X-Archive-Number: 200611/5 X-Sequence-Number: 23532 > >> Yes, 32 entries. >> > > Wow, that's the first case I've heard of where whole tables were left > around with no matching schema. You'll probably find you have to drop > both the pg_class and pg_type rows before pg_dump will work --- AFAIR > you shouldn't have to clean out pg_attribute. > > Thanks Tom. I was able to run pg_dump successfully after clearing those rows from the pg_class and pg_type tables. > Since it's hard to tell exactly what's going on here, I'd suggest a > pg_dumpall/initdb/reload sequence to be sure there isn't any other > undetected corruption. Be sure to check that the dump contains > everything you expect though. > Will do this. Sounds like there's some hairy stuff going on and a good cleanout would be a good idea (as well as a PG upgrade). Thanks again for your help. Peter