[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: [ADMIN] pg_dump: schema with OID 16396 does not exist
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2006-08-31 16:56:37
Message-ID: 9658.1157043397 () sss ! pgh ! pa ! us
[Download RAW message or body]

RW <postgres@tauceti.net> writes:
> > 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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@postgresql.org so that your
       message can get through to the mailing list cleanly


[prev in list] [next in list] [prev in thread] [next in thread]