Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id C3D769E8853 for ; Wed, 9 May 2012 11:20:36 -0300 (ADT) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SS7kp-0003si-Ha for pgsql-admin@postgresql.org; Wed, 09 May 2012 14:20:36 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q49EKMes019838; Wed, 9 May 2012 10:20:22 -0400 (EDT) To: Chander Ganesan cc: pgsql-admin@postgresql.org Subject: Re: pg_dump: schema with OID 2200 does not exist In-reply-to: <4FAA7815.2000900@gmail.com> References: <4FAA7815.2000900@gmail.com> Comments: In-reply-to Chander Ganesan message dated "Wed, 09 May 2012 09:58:45 -0400" Date: Wed, 09 May 2012 10:20:21 -0400 Message-ID: <19837.1336573221@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201205/47 X-Sequence-Number: 39536 Chander Ganesan writes: > I'm running into a weird issue with PostgreSQL 9.1.3 and PostGIS 2.0 > when trying to dump a table - no matter what table I try to dump in this > database, I find that I get the same error, as evidenced below (scroll > down for relevant data/error output.) 2200 would normally be the "public" schema. Since you show it having a different OID, I suppose you dropped and recreated it at some point. The question is, how did you manage to do that if there were still objects in it? Can you reproduce the sequence of events that led to this state of affairs? Since you mention moving things with ALTER EXTENSION, I wonder if there could be a bug in that, but this report is way too vague for somebody else to investigate. regards, tom lane