Hello once again,

Let's say you have many slaves being rep'd from a master.  Sometimes, one
of these slaves will fall behind in a big way.  Even stopping all activity
on all systems to allow it to catch up doesn't resolve the problem.

My question is the following:  from an admin point of view in trying to
resolve this kind of issue, what slony tables should I poke around in (and
what flag/s should I take note of), and what errors/footprints should I
look for in the slony logs which might be contributing to the node in
question never catching up?

My (horribly noob) solution so far has been to stop everything, drop
replication systems from all nodes, and start again (a process which can
throw a week in the drain).

Pointers and/or suggestions would be welcomed.  I've plodded through the
docs, but the obvious isn't jumping out at me, and my stupid approach to
solving the problem is wasting eons of time each time this occurs.

Thanks
Henry