From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chander Ganesan <chander.ganesan@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump: schema with OID 2200 does not exist
Date: Wed, 09 May 2012 10:20:21 -0400
Message-ID: <19837.1336573221@sss.pgh.pa.us> (raw)
In-Reply-To: <4FAA7815.2000900@gmail.com>
References: <4FAA7815.2000900@gmail.com>
Chander Ganesan <chander.ganesan@gmail.com> 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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, chander.ganesan@gmail.com
Subject: Re: pg_dump: schema with OID 2200 does not exist
In-Reply-To: <19837.1336573221@sss.pgh.pa.us>
* 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