On 05/16/2016 09:56 AM, Charles Clavadetscher wrote:
> Hello
>
> On 16.05.2016, at 18:32, Francisco Olarte <folarte@peoplecall.com
> <mailto:folarte@peoplecall.com>> wrote:
>
>> Hi Lucas
>>
>> On Mon, May 16, 2016 at 4:10 AM, Lucas Possamai <drum.lucas@gmail.com
>> <mailto:drum.lucas@gmail.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.
http://www.postgresql.org/docs/9.5/static/monitoring-stats.html
"
state text Current overall state of this backend. Possible values are:
active: The backend is executing a query.
idle: The backend is waiting for a new client command.
idle in transaction: The backend is in a transaction, but is not
currently executing a query.
idle in transaction (aborted): This state is similar to idle in
transaction, except one of the statements in the transaction caused an
error.
fastpath function call: The backend is executing a fast-path function.
disabled: This state is reported if track_activities is disabled in
this backend.
"
> Thank you and bye
> Charles
>
>> Francisco Olarte.
>>
>>
>>
--
Adrian Klaver
adrian.klaver@aklaver.com