<div dir="ltr"><div>Ok, thanks. :)</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 March 2015 at 09:28, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> OK, thanks.<br>
><br>
> That was it.<br>
><br>
> After reading documentarion I didn't get properly the connection pool from<br>
> pgpool. Now I know "num_init_children" is the number of accepted<br>
> connections from Psql clients.<br>
><br>
>>From what I understand, Pgpool's pool is not similar to other pools where<br>
> there are many external connections sharing fewer connections to backend.<br>
> Instead, Pgpool accepts external connections and then multiply them to the<br>
> backend! I dont get what is the advantage when you've got 'permanent'<br>
> external connections (unless the cached connections can be shared among<br>
> every child).<br>
<br>
</span>Pgpool expects that connections from client (for example psql) to<br>
pgpool are short lived. If those psql sessions use same user/database,<br>
the connections from pgpool to PostgreSQL can be reused. That's the<br>
idea.<br>
<span class=""><br>
> external connections (unless the cached connections can be shared among<br>
> every child).<br>
<br>
</span>Even if the cached connections are not shared among every child, there<br>
will be great chance to be reused by clients in the long run.<br>
<div class="HOEnZb"><div class="h5"><br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
</div></div></blockquote></div><br></div>