X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id B7AFF9FB367 for ; Thu, 31 Aug 2006 05:25:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 96924-03 for ; Thu, 31 Aug 2006 08:25:49 +0000 (UTC) X-Greylist: delayed 21:02:04.471764 by SQLgrey- Received: from www.tauceti.net (unknown [213.9.110.45]) by postgresql.org (Postfix) with ESMTP id 36A049FA12B for ; Thu, 31 Aug 2006 05:25:48 -0300 (ADT) Received: from [127.0.0.1] (scotty.tauceti.local [10.0.0.8]) by www.tauceti.net (Postfix) with ESMTP id 3601A8013A7 for ; Thu, 31 Aug 2006 10:25:45 +0200 (CEST) Message-ID: <44F69D08.80308@tauceti.net> Date: Thu, 31 Aug 2006 10:25:44 +0200 From: RW User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) 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> In-Reply-To: <26697.1156945365@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.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/343 X-Sequence-Number: 22886 Hi Tom, thanks for your answer. >> pg_dump: schema with OID 16396 does not exist > > I assume you don't see that OID in "select oid,nspname from pg_namespace"? > Yes, that's right. > 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. > > select * from pg_type where typnamespace = 16396 > > and likewise for pg_class.relnamespace, pg_operator.oprnamespace, > pg_conversion.connamespace, pg_opclass.opcnamespace, > pg_aggregate.aggnamespace, pg_proc.pronamespace. > 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) The owner is the user cms_mps_d_p. [postgres@host1202~]$ psql -d mps_dev -U cms_mps_d_p mps_dev=> \dc List of conversions Schema | Name | Source | Destination | Default? -------------+-----------------------------+---------------+---------------+---------- cms_mps_d_p | iso_8859_1_to_utf_8 | LATIN1 | UTF8 | yes ... Well I remember that our developers created such a function but they don't need it anymore. Could I simply drop it to solve the problem with pg_dump? But anyway... How can this be avoided and why does such a sitiation occur? I just dropped the database, created a new one (with the same name) and started a restore (completed with no errors). This procedure seems not so unusual to me ;-) And it happens the second time to me. Thanks, Robert