Peter Geoghegan <peter.geoghegan86 at gmail.com> writes:
> I'm experiencing a curious issue with Slony 2.0.2 . If I shut down a
> slave, and subsequently boot it back up, the sl_status view's event
> lag grows continually, as if replication isn't working between the
> master and that particular slave. However, replication is observably
> working. I can make the sl_status view's lag for the slave return to
> zero by restarting slon daemons.
>
> Why might this be? I find the sl_status view very important for my
> particular application.

Have you run test_slony_state to check the state of the cluster?

   http://slony.info/documentation/monitoring.html#TESTSLONYSTATE

It's likely that confirmations aren't getting back to the origin,
which tends to imply some form of misconfiguration or a network
problem.

That script should help give some idea as to where things are breaking
down.
-- 
let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;;
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"