On Thu, 2008-02-14 at 19:45 +0000, Christopher Browne wrote:
> Ow Mun Heng wrote:
> > Is there a way to manually force slony to switch from log_1 to log_2?
> > The table is getting way big (~1+G) and I think that it's causing the
> > "fetch 100 from log" to become slow ~60-150secs.
> >   
> You can request this from SQL prompt via:
> 
> select _my_slony_schema.logswitch_start();
> 
> It may fail with the error:
> ERROR: Previous logswitch still in progress
> 
> It will not immediately lead to cleaning out sl_log_1; that is handled 
> as part of the cleanup thread, which normally runs every 10 minutes 
> (controlled by a parameter compiled into slon).

It's been > 10 min (actually couple of hours since the last Forced
log_switch and yet the log_1 is still not being cleaned up.

So.. how can I rectify this?