From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
---|---|
To: | si24 <smrcoutts24(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connection pooling |
Date: | 2013-10-31 11:10:48 |
Message-ID: | CAJvUf_tW1qMP86VUgeg-ZnY91atOwtmrYNBwZL-kH3Na-wUhJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)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.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2013-10-31 11:53:57 | Re: Connection pooling |
Previous Message | si24 | 2013-10-31 11:00:27 | Re: Connection pooling |