Hi

I had to take replication on one of my DBs down for some days, and after
restarting it I have problems with it cactching up.

One of the problems I found is that sl_log_1 is cleaned up twice (and as
it results on 2 seqscans over a table of tens of millions of rows, it is a
real problem).

The query that does that is constructed starting at  cleanup_thread.c:144
in src of slony1-1.0.5.

Could it be that the other delete was actually meant for sl_log_2 ?

Why it decides to do it using seqscan is another puzzle for me.

The table is vacuum analysed quite often, but IIRC it has always done the
deleting using seqscan.

--------------
Hannu