<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 14, 2014 at 1:29 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":se" class="a3s" style="overflow:hidden">You can turn keep alive's off on the slon end with<br>
tcp_keepalive<br>
<br>
<a href="http://www.slony.info/documentation/2.2/slon-config-connection.html" target="_blank">http://www.slony.info/<u></u>documentation/2.2/slon-config-<u></u>connection.html</a><div style="width:16px;height:16px;display:inline-block">
</div><br></div></blockquote></div><br>I'm fairly sure this keep alive is a red herring here. In FreeBSD 9.1, postgres complains with the same getsockopt error, and all that does is cause postgres to not do the corresponding setsockopt. It makes no difference if you patch FreeBSD to have the getsockopt succeed.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Furthermore, setting the keeplalive timeout in freebsd down to 150 seconds doesn't cause the connection to fail sooner. In fact on my running systems, the timeout was 2 hours. So something else is funky going on here.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">FWIW, I did not recompile postgres or slony after upgrading to freebsd 9.2 from 9.1. Also, my master is still running 9.1 and never locks up. Something freebsd-related for sure.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">But i will try to disable slony's keepalive just in the slim chance that it is related.</div><div class="gmail_extra"><br></div></div>