pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: RW <postgres@tauceti.net>
To: pgsql-admin@postgresql.org
Subject: Re: pg_dump: schema with OID 16396 does not exist
Date: Fri, 01 Sep 2006 10:21:47 +0200
Message-ID: <44F7ED9B.7000005@tauceti.net> (raw)
In-Reply-To: <9658.1157043397@sss.pgh.pa.us>
References: <44F5753F.9080409@tauceti.net>
	<26697.1156945365@sss.pgh.pa.us>
	<44F69D08.80308@tauceti.net>
	<9658.1157043397@sss.pgh.pa.us>

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
>  
>




view thread (5+ messages)

Message-ID: <44F7ED9B.7000005@tauceti.net>
Permalink:  ../44F7ED9B.7000005@tauceti.net/
Also on:    postgresql.org/message-id/44F7ED9B.7000005@tauceti.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: postgres@tauceti.net
  Subject: Re: pg_dump: schema with OID 16396 does not exist
  In-Reply-To: <44F7ED9B.7000005@tauceti.net>
  References: <44F5753F.9080409@tauceti.net> <26697.1156945365@sss.pgh.pa.us> <44F69D08.80308@tauceti.net> <9658.1157043397@sss.pgh.pa.us> <44F7ED9B.7000005@tauceti.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox