<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-mailStijl17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NL link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>Is it possible to change the behaviour of handling of client connections when more than num_init_children try to connect? We have a number of applications using a drop wizard connection pool to connect to the pgpool-II cluster. In an ideal situation these applications would be sized to the maximum amount of available connection, but as said, this would be an ideal situation. In real life, some of these application try to allocate more connections then available, but instead of a connection error the application pool just waits for the connection to become active. As such, one misconfigured application can hold all the connections of the pool, blocking all other applications.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>It would be great if we could mimic the standard postgresql rejection or even better, put some timeout value for the queued connections. For instance, queue a new connection if no available pool processes for x time, reject after x time if no processes are freed to handle the queued connection. As such, the application pool would know that the extra connection didn’t succeed and would pool the request to one of the already open connections.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>An even better way of coping with this would be to be able to limit the amount of connections per user/database/ip. I still need to test what happens if you put a user limit in postgresql, for example, if you put a connection limit of 4 for user test on postgresql level, what happens if you try to open 5 connections to the pgpool with some processes left to handle connections. Does it reject the connection or does it queue it?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Sam</span><span style='mso-fareast-language:NL'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>