Re: Connection pooling

for some reason it not always pooling the connections for reuse so I'm not
sure what or if I have left something out.

As I only have a 100 postgres connections and when you have six people
working on it at the same time the connections neary go all the way. Which
in turn starts making pink tiles from geoserver so then its not reading the
data properly.

Geoserver itself seems to use 17 connections from postgres which is reading
the 17 different tables that each layer reads to create the map.

has it some thing to do with geoserver do I need to change something there
first. I can extend the max connections in postgres but if we ended up
having alot more people looking at the map I'm not to sure where the balance
would be.

It seems for each person that they seem to get about +-20 or more
connections each depending on there use of the map if they add the layers
that are overlyed over the map like zones etc...

--
View this message in context: http://postgresql.1045698.n5.nabble.com/Connection-pooling-tp5776378p5776498.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.