That seems to have taken care of it. Thanks so much. I ran the test_slony_state-dbi.pl and the sync age has cleared up.
On Monday 03 April 2006 16:22, Christopher Browne wrote: > Chris Mount <[EMAIL PROTECTED]> writes: > > 2006-04-03 10:09:09 CDT ERROR remoteWorkerThread_1: "select > > "_cpc_replic".sequenceSetValue(111,1,'106076','380399'); > > " PGRES_FATAL_ERROR PANIC: right sibling's left-link doesn't match > > CONTEXT: SQL statement "insert into "_cpc_replic".sl_seqlog (seql_seqid, > > seql_origin, seql_ev_seqno, seql_last_value) > > values ( $1 , $2 , $3 , $4 )" > > Searching for "right sibling's left-link doesn't match", I find > suggestions from Tom Lane to reindex tables. > > It sounds to me as though the failure corrupted an index on one of the > tables, probably _cpc_replic.sl_seqlog. > > Try reindexing it on the failing node, and see if that helps. > > Of course, where there's one corruption, there could be more... > > I'd suggest doing a vacuum of the whole thing via "VACUUM VERBOSE"; if > that runs into problems, you'll know... _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
