On Thu, Jun 26, 2014 at 8:15 AM, Steve Singer <ssinger at ca.afilias.info>
wrote:

>
>
> Which transactions are locking sl_log_2 when slony is in that state?
>
> The slony log trigger should only be adding rows to sl_log_1 in this
> state.   If this isn't the case then there is a problem.
>
> The problem with waiting for the lock is other transactions will the block
> and queue up behind the cleanup thread/transaction.
>
>
>
I saw this query from slony slave :

fetch 500 from LOG;

but another time it is

<IDLE> in transaction

that has lock on sl_log_2. The <IDLE> in transaction appear much more often.

-- 
Regards,

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