For where you are measuring, everything looks normal to me.
Your application will make connections to the pooler as needed, and the pooler will assign the application connection to a database connection it has available in it's pool. This gets rid of the overhead of creating a brand new connection to the DB right from the application for a small query, as connecting to the pooler is much less overhead.
The pooler should eventually get to the maximum number of allowed connections. That is just how it's supposed to work. It is not supposed to any connections after your application doesn't need the them any more. It just keeps it open, and adds it to the available pool for your application to use.
On Thu, Oct 31, 2013 at 10:49 AM, si24 <smrcoutts24@xxxxxxxxx> wrote:
I use a check in postgres to give the active connections being used.
But what happens if the connection pooler goes all the way to 100 for
example and say that 100 is your postgres maximum connections at the time. I
know I can change the maximum connections in postgres but am not to sure on
the right balance. If I have say 600 people looking at my map is that not
then several calles to postgres to show them the map that each person is
looking at on the computer?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Explanantion-on-pgbouncer-please-tp5776515p5776524.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
