Wow, Thanks a lot, that bug definitely what we experience. Will prepare for
upgrade.

On Fri, Apr 17, 2015 at 8:40 PM, Steve Singer <ssinger at ca.afilias.info>
wrote:

> On 04/16/2015 11:44 PM, Soni M wrote:
>
>> Hello All,
>> 2 nodes configured for slony 2.0.7, on RHEL 6.5 using postgres 9.1.14.
>> Each slon manage local postgres.
>> Slony and RHEL installed from postgres yum repo.
>>
>>
> Slony 2.0.x is no longer supported and was never properly supported
> against PG 9.1 +.  You should upgrade to 2.2
>
> Your issue looks a lot like bug 258 (
> http://www.slony.info/bugzilla/show_bug.cgi?id=258) which was fixed in
> the 2.1 and 2.2 series.
>
>
>
>  On some occasion, on master db, the cleanupEvent last for long time, up
>> to 5 minutes, normally it finish for a few seconds. The 'truncate
>> sl_log_x' is waiting for a lock which takes most time. This make all
>> write operation to postgres have to wait also, some get failed. As I
>> inspected, what makes truncate wait is another slon transaction made by
>> slon slave process, that is transaction which run 'fetch 500 from LOG'.
>> This transaction left 'idle on transaction' for a long time on some
>> occasion.
>>
>> Why is this happen ? Is this due to network latency between nodes ? Is
>> there any work around for this?
>>
>> Many thanks, cheers...
>>
>> --
>> Regards,
>>
>> Soni Maula Harriz
>>
>>
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at lists.slony.info
>> http://lists.slony.info/mailman/listinfo/slony1-general
>>
>>
>


-- 
Regards,

Soni Maula Harriz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20150417/1a08a724/attachment.htm