<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 26, 2014 at 8:15 AM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><br>
<br></div>
Which transactions are locking sl_log_2 when slony is in that state?<br>
<br>
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.<br>
<br>
The problem with waiting for the lock is other transactions will the block and queue up behind the cleanup thread/transaction.<br>
<br><br>
</blockquote></div><div class="gmail_extra"><br></div>I saw this query from slony slave :</div><div class="gmail_extra"><br></div><div class="gmail_extra">fetch 500 from LOG;</div><div class="gmail_extra"><br></div><div class="gmail_extra">
but another time it is </div><div class="gmail_extra"><br></div><div class="gmail_extra"><IDLE> in transaction<br></div><div class="gmail_extra"><div><br></div><div>that has lock on sl_log_2. The <IDLE> in transaction appear much more often.</div>
<div><br></div>-- <br><div dir="ltr"><div>Regards,</div><div><br></div>Soni Maula Harriz</div>
</div></div>