Re: Problem with pg_dump - Mailing list pgsql-general

From Andrew Sullivan
Subject Re: Problem with pg_dump
Date
Msg-id 20070522155454.GZ22797@phlogiston.dyndns.org
Whole thread Raw
In response to Problem with pg_dump  (znahor-news@netsync.pl)
Responses Re: Problem with pg_dump
Re: Problem with pg_dump
List pgsql-general
On Tue, May 22, 2007 at 04:36:49PM +0200, znahor-news@netsync.pl wrote:
> pg_dump on master works fine. On slave i've got error on start of
> dumping:
>
> -bash-3.00$ pg_dump -d -D my_database
> pg_dump: failed sanity check, parent table OID 225893092 of
> pg_rewrite entry OID 225893271 not found

You're using Slony, right?  You can't use pg_dump on a database where
_any_ table is Slony-replicated right now.  Yes, this is due to the
catalogue corruption Slony introduces.  There's an alternative in the
Slony tools/ directory.

A

--
Andrew Sullivan  | ajs@crankycanuck.ca
Everything that happens in the world happens at some place.
        --Jane Jacobs

pgsql-general by date:

Previous
From: Robert Fitzpatrick
Date:
Subject: Permance issues with migrated db
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Problem with pg_dump