From: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> |
---|---|
To: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: idle_in_transaction_timeout |
Date: | 2014-06-23 04:02:17 |
Message-ID: | 20140623040217.GI31357@toroid.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 2014-06-22 19:45:08 -0700, david(dot)g(dot)johnston(at)gmail(dot)com wrote:
>
> On Sunday, June 22, 2014, Kevin Grittner-5 [via PostgreSQL] <
> ml-node+s1045698n5808309h3(at)n5(dot)nabble(dot)com> wrote:
>
> > If we stick with the rule that what is to the left of _timeout is
> > what is being cancelled, the a GUC to cancel a transaction which
> > remains idle for too long could be called idle_transaction_timeout.
I (somewhat reluctantly) agree with Kevin that
"idle_in_transaction_session_timeout" (for FATAL) and
"idle_transaction_timeout" (for ERROR) would work.
The only other alternative I see is to use "idle_transaction_timeout"
now (even when we're killing the session) and later introduce another
setting named "idle_transaction_timeout_keep_session" (default false)
or something like that. (I'd prefer an extra boolean to something set
to 'session' or 'transaction'.)
> Idle_transaction_timeout has already been discarded since truly idle
> transactions are not being affected, only those that are in
> transaction.
I have no idea what this means.
-- Abhijit
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2014-06-23 04:53:29 | Re: pg_resetxlog to clear backup start/end locations. |
Previous Message | Tom Lane | 2014-06-23 03:02:57 | Re: tab completion for setting search_path |