If it is still accomplishing something (no errors and st_last_received
is advancing) then you can pump the -g value way up (say 10000) and that
should start to make headway even on a very large sl_log_1 by doing a
ton of work in a single pass (very long and large transactions).

Best of luck!

On Mon, 2006-01-16 at 17:58 -0800, Ujwal S. Setlur wrote:
> Hi all,
> 
> So I have this master/slave setup with replication
> going. One particular table is huge, ~50 million rows.
> It took about 24 hours for the slave to subscribe and
> catch up. But it did: st_num_lag_events came to 0.
> 
> Then the master got rebooted for some reason. Slony1
> was not in the startup scripts so it did not get
> launched for a day or so. I started it manually and
> expected the slave to catch up eventually. It hasn't.
> It has been about 4 days. st_num_lag_events is about
> 64000 and growing.
> 
> 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
> 
--