Hi Sethu, On Fri, Mar 21, 2014 at 6:51 PM, Sethu Prasad <sethuprasad.in@xxxxxxxxx> wrote: > So here the connection creation action is the costliest among all the other > management tasks. so keeping the connections ready is the best option. That's why you often have a minIdle parameter which allows to create idle connections in advance. > poolSize parameter is very good in the sense when the application owner know > what is the optimal number to put, after having application performance > analysed with the history of previous settings and the improvements made on > it. server sizing always shows up in this sort of analysis. It supposes that you do this job. From my experience, most of the "not so demanding" apps are put into production without this sort of detailed analysis. You do it for your critical high throughput applications, not for the others. That said, interesting discussion. Not exactly what I expected. -- Guillaume -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
