Check the archives. There's a couple paramaters you can tune to help the
situation (IIRC -g is one of them).

On Sat, Mar 18, 2006 at 08:02:25AM -0800, Ujwal S. Setlur wrote:
> Hi,
> 
> The slon process on my subscriber had terminated
> complaining about a server process having crashed. We
> noticed this after only about 10 days. I guess I need
> to do something about that.
> 
> I then restarted slon on both origin and subscriber,
> but the subscriber is not catching up. I am monitoring
> the sl_lag_time, and every now and then, it goes down,
> but not by much. Mostly it is slowly going up.
> 
> The origin is getting fed with quite a bit of data, so
> maybe slon is finding it hard to catch up?
> 
> I am using slon 1.1.5 on postgresql 8.0.3. I am also
> using a "g" value of 100.
> 
> Any ideas?
> 
> Thanks,
> 
> Ujwal
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
> 

-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby at pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461