On Tue, Mar 18, 2014 at 8:59 AM, Vick Khera <vivek at khera.org> wrote:

> after locking the set and restarting the slon daemons, I waited about 4
> minutes yet the cleanup never happened.
>
> do i need to let the slons run with short cleanup set for a while before I
> try the upgrade? ie, clear out any 10 minute timeouts somewhere?
>

It appears if I wait until there are 0 backlogged events, and I manually
run cleanupevent('10 seconds'::interval) four times, both tables get
truncated immediately. i will try this on my next maintenance interval on
production.

is something else preventing cleanupevent() from completing? on my
produciton it looks as if the lock; cleanupevent(); commit sequence sits
idle (not waiting on a lock) for a few minutes then executes and start over
again idle for a while again, even with the interval of 10 seconds.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20140318/cdb9420a/attachment.htm