> We get very good performance dealing with
> thousands of concurrent users with a pool of 35 connections to the
> 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.
In response to
pgsql-admin by date
|Next:||From: Chander Ganesan||Date: 2012-05-09 13:58:45|
|Subject: pg_dump: schema with OID 2200 does not exist|
|Previous:||From: Kevin Grittner||Date: 2012-05-08 17:29:23|
|Subject: Re: increasing max_pred_locks_per_transaction, what
shuold I look for?|