Re: idle in transaction, why

From: Rob Sargent <robjsargent(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: idle in transaction, why
Date: 2017-11-06 20:24:32
Message-ID: 6ed9ca9b-fb80-e505-2522-be9b5f63a759@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 11/06/2017 01:17 PM, Tom Lane wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)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)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2017-11-06 20:35:03 Re: postmaster deadlock while logging after syslogger exited
Previous Message Rob Sargent 2017-11-06 20:18:47 Re: idle in transaction, why