X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 740069FB469 for ; Fri, 1 Sep 2006 05:22:39 -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 36591-05-2 for ; Fri, 1 Sep 2006 05:21:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from www.tauceti.net (unknown [213.9.110.45]) by postgresql.org (Postfix) with ESMTP id 8B6E19FB470 for ; Fri, 1 Sep 2006 05:21:47 -0300 (ADT) Received: from [10.0.0.123] (unknown [10.0.0.123]) by www.tauceti.net (Postfix) with ESMTP id 53D4B800C3D for ; Fri, 1 Sep 2006 10:21:44 +0200 (CEST) Message-ID: <44F7ED9B.7000005@tauceti.net> Date: Fri, 01 Sep 2006 10:21:47 +0200 From: RW User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: pg_dump: schema with OID 16396 does not exist References: <44F5753F.9080409@tauceti.net> <26697.1156945365@sss.pgh.pa.us> <44F69D08.80308@tauceti.net> <9658.1157043397@sss.pgh.pa.us> In-Reply-To: <9658.1157043397@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.168 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/2 X-Sequence-Number: 22916 Hi Tom, deleted entry from pg_conversion. Problem solved. pg_dump works again. Thanks, Robert Tom Lane wrote: >>>Look through the system catalogs to find the object(s) that claim to be >>>in that namespace, and then tell us what they are and their history. >>> >>> > > > >>Found it in pg_conversion: >> >> > > > >>mps_dev=# select * from pg_conversion where connamespace = 16396; >> conname | connamespace | conowner | conforencoding | >>contoencoding | conproc | condefault >>---------------------+--------------+----------+----------------+---------------+-------------------+------------ >> iso_8859_1_to_utf_8 | 16396 | 16389 | 8 >>| 6 | iso8859_1_to_utf8 | t >>(1 row) >> >> > > >Ah. This is a known bug: CREATE CONVERSION neglected to enter a dependency >from the new conversion to its namespace, hence a DROP SCHEMA on the >namespace would not remove the pg_conversion entry. This is fixed in >HEAD but hasn't been back-patched for some reason --- I'll go deal with >that now. > >In the meantime I'd suggest a manual DROP CONVERSION to clean up ... >hmm ... except you probably can't name that conversion anymore in SQL, >what with it not having a schema. I think it would work well enough to >just DELETE the specific row in pg_conversion. > > regards, tom lane > >