I am using slony-1.1.0 with postgresql-8.0.6 and have a situation that I hope has a better resolution than I am currently using.
One of my 2 slaves is some distance away and over the last 6 months or so we have had quite a few network brown or black outs between it and the master. After such an event, replication fails and the only way I am managing to get it to go again is to drop the node and database and start again. I have done this now so many times I have scripted it so that I can get the slave back online relatively quickly. I get errors, like the following, in the slony log 2006-01-26 08:11:13 NZDT ERROR remoteWorkerThread_1: "start transaction; set enable_seqscan = off; set enable_indexscan = on; " PGRES_FATAL_ERROR 2006-01-26 08:11:13 NZDT ERROR remoteWorkerThread_1: "close LOG; " PGRES_FATAL_ERROR 2006-01-26 08:11:13 NZDT ERROR remot eWorkerThread_1: "rollback transaction; set enable_seqscan = default; set enable_indexscan = default; " PGRES_FATAL_ERROR 2006-01-26 08 :11:13 NZDT ERROR remoteWorkerThread_1: helper 1 finished with error 2006-01-26 08:11:13 NZDT ERROR remoteWorkerThread_1: SYNC aborted Stopping and restarting all the various slony processes doesn't seem to clear things. NB: It only ever seems to happen after a network event. Any advice on how to get replication started again without rebuilding would be appreciated. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Glen and Rosanne Eustace, GodZone Internet Services, a division of AGRE Enterprises Ltd., P.O. Box 8020, Palmerston North, New Zealand 5301 Ph/Fax: +64 6 357 8168, Mob: +64 27 5 424 015, Web: www.godzone.net.nz "A Ministry specialising in providing low-cost professional Internet Services to NZ Christian Churches, Ministries and Organisations" _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
