X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (unknown [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 69FC29FB2B8 for ; Wed, 30 Aug 2006 08:53:03 -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 20489-06-2 for ; Wed, 30 Aug 2006 08:52:29 -0300 (ADT) X-Greylist: delayed 00:26:06.279687 by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 3CC189FB2FB for ; Wed, 30 Aug 2006 08:49:57 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from www.tauceti.net (unknown [213.9.110.45]) by svr4.postgresql.org (Postfix) with ESMTP id AFF055AF8A4 for ; Wed, 30 Aug 2006 11:23:50 +0000 (GMT) Received: from [127.0.0.1] (scotty.tauceti.local [10.0.0.8]) by www.tauceti.net (Postfix) with ESMTP id 6630B800C2A for ; Wed, 30 Aug 2006 13:23:43 +0200 (CEST) Message-ID: <44F5753F.9080409@tauceti.net> Date: Wed, 30 Aug 2006 13:23:43 +0200 From: RW User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: pg_dump: schema with OID 16396 does not exist 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/326 X-Sequence-Number: 22869 Hi everybody, I have a problem with pg_dump. After dropping a database (DROP DATABASE ...) I've created the database again (CREATE DATABASE ...) and restored a dump which we create every night. No problem so far and import was no problem and without errors. But now it isn't possible to make a backup because of the following error: pg_dump: schema with OID 16396 does not exist Postgres version is 8.1.4 and OS is Redhet ES 4 U3. I've already had the same problem on a completely different database (Version 8.1.3) on a different host same szenario. But in this case I've had the possibility to drop the entire cluster, started a initdb and do the restore. Problem solved. This is not possible with this cluster so I need a real solution for the problem. When I look at pg_namespace mps_dev=# select * from pg_namespace ; nspname | nspowner | nspacl --------------------+----------+------------------------------------------------------- pg_toast | 10 | pg_temp_1 | 10 | pg_catalog | 10 | {postgres=UC/postgres,=U/postgres} information_schema | 10 | {postgres=UC/postgres,=U/postgres} as_mps_d_p | 16387 | cms_mps_d_p | 16389 | {cms_mps_d_p=UC/cms_mps_d_p,as_mps_d_p=U/cms_mps_d_p} public | 10 | {postgres=UC/postgres,=UC/postgres} (7 rows) there is no nspacl for schema as_mps_d_p. Seems strange to me. Thanks for any hint. - Robert