From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem with pg_dump |
Date: | 2007-05-22 16:00:12 |
Message-ID: | 4653138C.4080206@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andrew Sullivan wrote:
> 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.
*cough*
catalog features Slony adds.
Joshua D. Drake
>
> A
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2007-05-22 16:14:56 | Re: Problem with pg_dump |
Previous Message | Andrew Sullivan | 2007-05-22 15:54:55 | Re: Problem with pg_dump |