| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rob Sargent <robjsargent(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:09:27 |
| Message-ID: | CAKFQuwaOZPo6ArqXrJ=E1jVYxV-F9=YuY8uypyY+OymuZAKKsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Nov 6, 2017 at 12:32 PM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
> Using postgres 10-beta3 (hopefully 10.0 this week) on virtual CentOS7 and
> this JDBC driver postgresql:42.1.4
>
>
> The postgresql.conf file has
>
> #idle_in_transaction_session_timeout = 0 # in milliseconds, 0 is
> disabled
>
>
There are numerous places where default settings can be configured.
https://www.postgresql.org/docs/10/static/config-setting.html
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-06 20:17:47 | Re: idle in transaction, why |
| Previous Message | David Pacheco | 2017-11-06 19:47:53 | postmaster deadlock while logging after syslogger exited |