Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: "'Kevin Grittner'" <Kevin.Grittner@wicourts.gov>,
	<pgsql-admin@postgresql.org>
References: <00da01cd2ce7$35d17780$a1746680$@com>
	<00e101cd2cfc$b6140b00$223c2100$@com>
	<4FA8E99B0200002500047A16@gw.wicourts.gov>
In-Reply-To: <4FA8E99B0200002500047A16@gw.wicourts.gov>
Subject: Re: Advice/guideline on increasing shared_buffers and kernel
	parameters
Date: Wed, 9 May 2012 16:11:10 +0530
Organization: Zoniac Software Private Limited
Message-ID: <001f01cd2dd0$4187f8d0$c497ea70$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Ac0tKE+KX05bOga/RNq3MAUgXnr06QApgvhQ
Content-Language: en-us

> We get very good performance dealing with
> thousands of concurrent users with a pool of 35 connections to the
> database.
> 
> If you want to handle more users than you can currently support, you
> probably need to use fewer database connections.

First, please excuse me that I'm not able to understand this particular
point clearly. How can be reducing/using fewer connections in connection
pooler can support larger concurrent incoming connection requests?  If this
is so critical to revisit (reducing), then I may have to convince/justify my
peers also, before making this change in the Production server.  Can you
throw some light on this subject?

Thanks for bringing this idea to notice.