[pgpool-general: 5441] Re: Testing max_pool and and num_init_children

Piotr Gbyliczek P.Gbyliczek at node4.co.uk
Wed May 3 19:36:09 JST 2017


On Tuesday, 2 May 2017 16:38:48 BST Lucas Luengas wrote:
> I think it's the expected behaviour[...]

It is. 

Basically, pgpool will start num_init_children number of processes, each 
holding max_pool pools that keep connections to each backend. 

max_pool determines how many user/password pairs will be cached, therefore 
controlling number of connection pgpool maintains to backends

num_init_children determines how many connection clients can make to pgpool 
There is a queuing mechanism, which has another limit to it before yo will get 
connection refused. This is controlled via listen_backlog_multiplier.

Regards,
Piotr

--

Piotr Gbyliczek
Solutions Engineer

Node4 Ltd, The POD, 10 Bottle Ln, Nottingham NG1 2HL
ddi. 08454 210444 | t. 0845 123 2222
e. P.Gbyliczek at node4.co.uk



Node4 Limited is registered in England No: 04759927 and has its registered office at Millennium Way, Pride Park, Derby, DE24 8HZ
The information contained in this email is confidential and is intended for the exclusive use of the email addressee shown.
If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited.
If you have received this mail in error, please notify our mail manager at abuse at node4.co.uk and delete it from your system.
Opinions expressed in this email are those of the individual not the company, unless specifically indicated to that effect.

This email has been scanned inbound by Node4's Email Security System.

This email message has been delivered safely and archived online by Mimecast.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361104009.png
Type: image/png
Size: 1315 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361104209.png
Type: image/png
Size: 16076 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361104509.png
Type: image/png
Size: 16233 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361104909.png
Type: image/png
Size: 17391 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361105209.jpg
Type: image/jpeg
Size: 21109 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361105409.jpg
Type: image/jpeg
Size: 29300 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361105609.png
Type: image/png
Size: 16168 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 117050311361105809.png
Type: image/png
Size: 19451 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170503/c59aabbd/attachment-0011.png>


More information about the pgpool-general mailing list