Our installation of slony 1.2.0 is struggling.

It started trying to do a log switchover several days ago. Since then,
every 10-20 minutes we get this in the logs:

NOTICE:  Slony-I: log switch to sl_log_2 still in progress - sl_log_1 not truncated

Between each time, it looks like it's doing a DELETE on both logs and a
VACUUM on sl_log_1.

sl_log_status on the master node is 3, which from the code means
everything should be going into sl_log_2, right? And yet /both/ logs are
continually growing, aside from the periodic DELETEs.

What's going on? Is this expected behavior? The way I understand it,
only one log should be growing and the other should be getting cleaned
out as the events in it propogate and are deleted.

I'm hoping that eventually a log switchover will be able to complete,
but it doesn't look like that's going to happen as long as things are
still getting put into the inactive log.

There aren't any long-running transactions on any of the nodes.

Ideas?

I ran into the problem at
http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1591,
before applying my patch as shown there. Could that have messed up the
log switch process and left it only partially switched somehow?

-- 
paul