<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Aug 2015, at 02:25, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org" class="">ishii@postgresql.org</a>> wrote:</div><div class=""><br class="">Great. I'm also interested in if my patch somewhat enhances<br class="">performance.<br class=""></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">“Somewhat” would be the understatement of the year in our scenario:</div><div class=""><br class=""></div><div class=""><a href="http://imgur.com/a/EzTB3" class="">http://imgur.com/a/EzTB3</a></div><div class=""><br class=""></div><div class="">Upgraded from pgpool2 3.3.6 to 3.3.7 including your semaphore patch. Switchover is clearly visible in the graphs.</div><div class=""><br class=""></div><div class="">If there are no adverse effects/broken features (idle timeouts?) due to your patch I highly recommend integrating it both in 3.3 and 3.4, at least as compiletime or config option </div><div class=""><br class=""></div><div class="">best,</div><div class="">Michael</div></body></html>