Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 438989FB2EE for ; Fri, 27 Oct 2006 13:40:10 -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 35494-07 for ; Fri, 27 Oct 2006 13:40:02 -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 8EDA89F9F96 for ; Fri, 27 Oct 2006 13:40:02 -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 k9RGdrlE006802; Fri, 27 Oct 2006 12:39:53 -0400 (EDT) To: Peter Neish cc: pgsql-admin@postgresql.org Subject: Re: pg_dump: schema with OID xxxxxxxx does not exist In-reply-to: <45418477.2020400@austehc.unimelb.edu.au> References: <45418477.2020400@austehc.unimelb.edu.au> Comments: In-reply-to Peter Neish message dated "Fri, 27 Oct 2006 14:00:55 +1000" Date: Fri, 27 Oct 2006 12:39:53 -0400 Message-ID: <6801.1161967193@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.202 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS, SUBJECT_NOVOWEL X-Spam-Level: X-Archive-Number: 200610/195 X-Sequence-Number: 23498 Peter Neish writes: > entity_browse_bid_seq | 37647910 | 1005 | 4 | t | > c | t | , | 37894096 | 0 | record_in | > record_out | record_recv | record_send | i | p | > f | 0 | -1 | 0 | | > entity_browse | 37647910 | 1005 | 4 | t | > c | t | , | 37894098 | 0 | record_in | > record_out | record_recv | record_send | i | p | > f | 0 | -1 | 0 | | > (2 rows) > Does this mean that I can just delete these rows from this table for the > dump to work? Will deleting these rows affect anything else? These are composite-type entries, which means there should be associated entries in pg_class --- with OIDs 37894096 and 37894098 respectively. Did you check to see if those are still there? We've seen scattered reports of table rowtype entries not being removed when the owning table is dropped, but no one's ever been able to make a reproducible case :-(. Do you know anything about the history or usage of these tables? regards, tom lane