Re: [GENERAL] idle in transaction, why - Mailing list pgsql-general

From Rob Sargent
Subject Re: [GENERAL] idle in transaction, why
Date
Msg-id 6ed9ca9b-fb80-e505-2522-be9b5f63a759@gmail.com
Whole thread Raw
In response to Re: [GENERAL] idle in transaction, why  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] idle in transaction, why
List pgsql-general
On 11/06/2017 01:17 PM, Tom Lane wrote:
> "David G. Johnston" <david.g.johnston@gmail.com> writes:
>> You should probably login as your application user and do "show
>> idle_in_transaction_session_timeout" to see what a clean session has for a
>> value and then figure out from there where that value is coming from.
> You don't have to guess about the latter: the pg_settings view will tell
> you exactly where the active value came from.  See the source, sourcefile,
> sourceline columns.
>
>             regards, tom lane
select name, setting, source, sourcefile, sourceline, extra_desc, 
context from pg_settings where name ~ 'idle';                name                 | setting | source  | sourcefile | 
sourceline |              extra_desc               | context

-------------------------------------+---------+---------+------------+------------+---------------------------------------+---------
idle_in_transaction_session_timeout| 0       | default |            
 
|            | A value of 0 turns off the timeout. | user tcp_keepalives_idle                 | 7200    | default |
      
 
|            | A value of 0 uses the system default. | user
(2 rows)



-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: [GENERAL] idle in transaction, why
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] postmaster deadlock while logging after syslogger exited