Re: Problem with pg_dump

Andrew Sullivan wrote:
> 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.

I'll be - I've obviously never tried pg_dump-ing a slave node. It does
say it here in black-and white though:

"This represents something of a "corruption" of the data dictionary, and
is why you should not directly use pg_dump to dump schemas on subscribers."
http://slony.info/adminguide/slony1-1.2.6/doc/adminguide/slonyintro.html

--
   Richard Huxton
   Archonet Ltd