Andrew Sullivan wrote:
On Tue, May 22, 2007 at 04:36:49PM +0200, [EMAIL PROTECTED] 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/
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
