http://www.slony.info/bugzilla/show_bug.cgi?id=292

--- Comment #4 from Jan Wieck <janwieck at yahoo.com> 2013-06-18 03:34:54 PDT ---
Slony cannot complete the log switch if either a replica does not catch up or
if there are long running transactions in the database, that began before the
log switch started. In the latter case, such long running transaction could
have created yet uncommitted log rows in the old  log table.

Make sure your application commits/rolls back all transactions. Even read only
ones. Not only Slony, but also autovacuum suffer from that application
misbehavior.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.