From: | Charles Clavadetscher <clavadetscher(at)swisspug(dot)org> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | Lucas Possamai <drum(dot)lucas(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Connections - Postgres 9.2 |
Date: | 2016-05-16 16:56:35 |
Message-ID: | A956FE23-E541-4E5D-BE91-3842DA6E41F6@swisspug.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
> On 16.05.2016, at 18:32, Francisco Olarte <folarte(at)peoplecall(dot)com> wrote:
>
> 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 ).
>
There really is a state 'Idle in transaction'? Good to learn.
Thank you and bye
Charles
> Francisco Olarte.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Olarte | 2016-05-16 17:09:23 | Re: Connections - Postgres 9.2 |
Previous Message | Francisco Olarte | 2016-05-16 16:32:06 | Re: Connections - Postgres 9.2 |