| From: | Venkata Balaji N <nag1010(at)gmail(dot)com> |
|---|---|
| To: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Charles Clavadetscher <clavadetscher(at)swisspug(dot)org>, Francisco Olarte <folarte(at)peoplecall(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Connections - Postgres 9.2 |
| Date: | 2016-05-16 20:56:44 |
| Message-ID: | CAEyp7J-TJWyMKX_3ZEGzSX+cfq+mORnDOiADQyQw0Q=6sAKGDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, May 17, 2016 at 6:28 AM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>
wrote:
> hmm.. thanks for all the answers guys...
>
>
> One more question: Those IDLE connections.. are using the server's
> resources?
> To solve that problem I would need a Pool connection, right?
>
> Would the pool connection solve that IDLE connections? But more important
> than that, are the IDLE connections using the machine's resources ?
>
Yes. There is no straight way to terminate the IDLE connections from the
database end. You would need a connection pooler like pgBouncer which can
help you terminate IDLE connections after a certain time.
It would be much better if your Application can terminate connections to
the database.
Regards,
Venkata B N
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-05-16 21:00:56 | Re: Connections - Postgres 9.2 |
| Previous Message | Adrian Klaver | 2016-05-16 20:55:46 | Re: Connections - Postgres 9.2 |