| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: idle in transaction, why |
| Date: | 2017-11-06 20:41:32 |
| Message-ID: | 19493.1510000892@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Rob Sargent <robjsargent(at)gmail(dot)com> writes:
> idle_in_transaction_session_timeout | 0 | default |
> | | A value of 0 turns off the timeout. | user
Meh. I think we're barking up the wrong tree anyway: so far as I can
find, there is no error message reading 'idle transaction timeout'
in the existing PG sources (and I sure hope no committer would have
thought that such an ambiguous message text was satisfactory).
So I think your error is coming from client-side or third-party code.
What other moving parts have you got in there?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2017-11-06 20:50:25 | Re: idle in transaction, why |
| Previous Message | Tom Lane | 2017-11-06 20:35:03 | Re: postmaster deadlock while logging after syslogger exited |