Re: Connection pooling
От | Gavin Flower |
---|---|
Тема | Re: Connection pooling |
Дата | |
Msg-id | 527244D5.1090201@archidevsys.co.nz обсуждение исходный текст |
Ответ на | Re: Connection pooling (Rémi Cura <remi.cura@gmail.com>) |
Ответы |
Re: Connection pooling
|
Список | pgsql-general |
On 01/11/13 00:10, Rémi Cura wrote:
making & breaking connections costs elapsed time & processor activity etc. - which is why they should be pooled for reuseHey,I might be completly wrong, but when you say"get the connections to close if they are not being used",I'd say that it is a bad client design to not close a connection when it doesn't need it anymore.The client should retrieve the data or close when not using after a certain amount of time.What you are trying to do is garbage collector.Cheers,Rémi-C2013/10/31 si24 <smrcoutts24@gmail.com>I'm not 100% sure I follow in that part of if its the client cause currently
when I run it on my own computer it does the same thing. Only when I stop
tomcat and start it again then i get the 3 default connection that postgres
has set up. our server does the same thing.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Connection-pooling-tp5776378p5776490.htmlSent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Cheers,
Gavin
В списке pgsql-general по дате отправления: