Re: Problem with pg_dump

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with pg_dump
Date: 2007-05-22 15:54:55
Message-ID: 20070522155454.GZ22797@phlogiston.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 22, 2007 at 04:36:49PM +0200, znahor-news(at)netsync(dot)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(at)crankycanuck(dot)ca
Everything that happens in the world happens at some place.
--Jane Jacobs

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2007-05-22 16:00:12 Re: Problem with pg_dump
Previous Message Robert Fitzpatrick 2007-05-22 15:17:40 Permance issues with migrated db