Hi,

We have a production system where our Slony replication process (one
master to one slave) appears to be falling behind. The sl_log_1 table
on the master keeps increasing in size while the slave is consistently
100% utilized. The slave appears to be executing update/insert/delete
statements that have been queued up by Slony.

I'm not sure how to go about troubleshooting whether slony is just
falling behind or if it is not replicating at all.

I suspect a new nightly process that batch deletes and loads hundreds
of thousands of records could've caused this behavior, and the tables
involved in this process should not be replicated by Slony. If I were
to remove this table from the replication set (using the SET DROP
TABLE slonik script), would that automatically help Slony replication
catch up? How does Slony handle pending updates when you remove an
affected table from the replication set.


-- 
---
John L Cheng