<div dir="ltr">We host several applications on the same DB. Sometimes folks apply patches/update to some databases by directly connecting to the DB instead of through pgpool. To fix the problem, I have to restart the service which brings down all the applications connected to the pgpool service. These applications now have to create brand new DB connections to continue working which is pretty drastic. <div><br></div><div>Having an option to reset cache in such a scenario without bringing the service down is convenient. Then I just have to take a performance hit till the cache warms up again.</div><div>-AJ</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 18, 2017 at 3:16 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@sraoss.co.jp" target="_blank">ishii@sraoss.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Is there a way to reset the entire cache without restarting the pgpool<br>
> service using SQL when using shmem?<br>
<br>
</span>No. Sorry. Why do you need it?<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_<wbr>en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.<wbr>jp</a><br>
</blockquote></div><br></div>