After enabling replication for a large database, I'm consistently seeing a
state where logs will not switch.  sl_log_1 contains some decent number of
rows (a few thousand), and sl_log_2 is growing.  Executing
_replication.logswitch_start() and finish() has no effect, as both report
switch still in progress.  This continues for days, until eventually there
are millions of rows in sl_log_2, and sync times take 15s or more just to
fetch rows to apply to the slave.

Thoughts?

  Scott Miller
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-bugs/attachments/20090108/220=
a412a/attachment.htm