Where are you measuring the connections? From your app to PGBouncer, or from PGBouncer to PostgreSQL?
If it is from your app to PGBouncer, that sounds strange, and like the app is not properly releasing connections as it should. If it is from PGBouncer to PostgreSQL, that sounds normal. I haven't used PGBouncer, but i've used other connection poolers in the past. They would start out with a set number of minimum connections, and scale up to the max number specified as needed. The pooler wouldn't release a connection to the DB once it has made one, and just kept it available in the pool.On Thu, Oct 31, 2013 at 10:25 AM, si24 <smrcoutts24@xxxxxxxxx> wrote:
Can some one please give me a bit more of a better explanation on how exactly
the pgbouncer works as I am now lost.
I'm not sure if it is pooling the connections cause surely if its not being
used the connections should go down not up i.e i run the webpage which has
my map running which is an open layers map reading geoserver all my data on
geoserver is from a database in postgres. When you start the web page it
goes to 46 connections and after moving around for a while and selecting the
different overlays that I have on the map it goes up to 75 connections after
not touching it for a while nothing happens the connections don't go up or
down, but when I move the map around and zoom then the connections increase
again to 84 connections.
Please help I'm stuck
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Explanantion-on-pgbouncer-please-tp5776515.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
