One more thing: after I'd already dropped the slave node, I was running through all the slony tables, and found something incredibly disturbing. On the master, though sl_log_1 was at 4.2M records, it's sl_seqlog was at a sobering 10.1M... I would that this is supposed to get cleaned-out when replication is caught-up. Anyway, another piece to the puzzle. Off I go to re-add the slave node.
-- Best Regards, Dan Falconer "Head Geek", AvSupport, Inc. (http://www.partslogistics.com) _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
