Hi Venkat I found a way to get Slony out of this state without rebuilding the db.
1) Connect to your database, e.g. psql <dbname> as user postgres 2) delete from _schema.sl_log_1; 3) select _schema.logswitch_finish(); 4) select _schema.logswitch_start(); Replace _schema with the name of your cluster schema. Kind regards, Tim -- Tim Lloyd CensorNet Ltd +44 (0) 845 230 9590 / [email protected] www.censornet.com (sent from my laptop) _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
