| From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
|---|---|
| To: | Jayadevan <maymala(dot)jayadevan(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Connection pooling |
| Date: | 2013-10-31 10:50:48 |
| Message-ID: | CAJvUf_va4owQyqFHZrUWgOWHp=PuKKU+7FU0qEorxsTEV1uUcQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Isn'it a client problem?
It should be client application closing connection when done with data
retrieval, and not the other way around?
Cheers,
Rémi-C
2013/10/31 Jayadevan <maymala(dot)jayadevan(at)gmail(dot)com>
> I have never used pgbouncer myself. But my guess is you have to look at the
> Timeout parameters in the configuration file.
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Connection-pooling-tp5776378p5776481.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 | si24 | 2013-10-31 10:57:04 | Re: Connection pooling |
| Previous Message | Raphael Bauduin | 2013-10-31 10:46:12 | problem with partitioned table and indexed json field |