<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">[moving this from pg-general to slony1-general on the off chance it's more related to slony...]<div><br><div><div>On Jan 15, 2010, at 8:41 AM, Scott Marlowe wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Fri, Jan 15, 2010 at 7:45 AM, Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> wrote:<br><blockquote type="cite">Ben Chobot <<a href="mailto:bench@silentmedia.com">bench@silentmedia.com</a>> writes:<br></blockquote><blockquote type="cite"><blockquote type="cite">We have recently discovered a problem with our slony-1 cluster of 8.1.19<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">installs. Specifically, we are unable to vacuum a table on the master<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">node; vacuum always hangs on the same index of the same table. If we do a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">slony switchover and make the other node the master, then *it* will become<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">unable to vacuum that index. Vacuum on the slave always works quickly and<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">without issue. Vacuum does not hang anywhere else.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">When we tried to strace the vacuuming backend, it appeared as if it was<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">trying to acquire a lock, but pg_lock showed nothing unexpected for that<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">index.</blockquote></blockquote><font class="Apple-style-span" color="#006312"><br></font>I've seen a situation like there during ddl ops (using the slony<br>execute command to run them on the cluster) where slony halts waiting<br>on vacuum and everything else halts waiting on slony. That was with<br>slony 1.2<br><br>With slony 2.0.3 or so, I had occasional complete lockups of my<br>database that I didn't have time to troubleshoot as it was a live<br>cluster and I had to restart slony and the databases to get them back<br>up and running.<br></div></blockquote></div><br></div><div>We're using slony 1.2.15, for what that's worth. I don't see anything in the 1.2.x release notes that would indicate any problem like this, but I'm new to slony.</div><div><br></div></body></html>