Re: Connection pooling
| От | Rémi Cura |
|---|---|
| Тема | Re: Connection pooling |
| Дата | |
| Msg-id | CAJvUf_tW1qMP86VUgeg-ZnY91atOwtmrYNBwZL-kH3Na-wUhJg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Connection pooling (si24 <smrcoutts24@gmail.com>) |
| Ответы |
Re: Connection pooling
|
| Список | pgsql-general |
Hey,
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-C
2013/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
В списке pgsql-general по дате отправления: