Nickolay,

Thanks for your reply. Can you let me know, when the sl_log_1 and
sl_log_2 gets empty.

The function logswitchfinish check for row count in both the tables
before truncating sl_log_1 and sl_log_2. But we never found them
getting empty. When we set the cleanup parameter things started
working properly.

Regards,
Nimesh

On 1/12/09, Nickolay <info at zhukcity.ru> wrote:
> Nimesh,
>
> Be careful with cleanup_deletelogs parameter.
> In my experience replication did not work properly with this parameter
> turned on.
> It would erase even some unconfirmed log entries which would cause lost
> (not replicated) transactions and rows on slave nodes.
>
>
> Nimesh Satam wrote:
> > Steven,
> >
> > We faced a similar kind of problem with the slony version 2.0.0.
> >
> > In order to solve the problem we have set the slon parameter
> > "cleanup_deletelogs" in the slony config file. You can then pass the
> > file path to the slon through the '-f' param.
> >
> > "cleanup_deletelogs=ON"
> >
> > This is a boolean variable and deletes logs which are older than a
> > particular transaction id.
> >
> > Regards,
> > Nimesh.
> >
>
> --
> Best regards, Nickolay.
>
>