| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Connections - Postgres 9.2 |
| Date: | 2016-05-16 16:32:06 |
| Message-ID: | CA+bJJbzmb_atz5mTn2X3XnhWTLc0g0swgDOG6htbiDmyWLz9ng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Lucas
On Mon, May 16, 2016 at 4:10 AM, Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>
wrote:
>
> Those IDLE connections, might be because the user/application didn't
> commit the transaction?
>
IIRC Those would be 'Idle in transaction' ( which are normally bad if
numerous, unless your app has a reason for them, as they are the ones which
can block things ). Plain 'Idle' are normally connections between
transactions, totally normal if you use poolers, or if your app keeps
connection opens while it does other things ( like preparing for a
transaction ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Clavadetscher | 2016-05-16 16:56:35 | Re: Connections - Postgres 9.2 |
| Previous Message | Pavel Stehule | 2016-05-16 16:31:53 | Re: Toolchain for extensions (language C, Visual Studio 2013 / 2015) |