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 [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
