Re: Feature thought: idle in transaction timeout - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Feature thought: idle in transaction timeout
Date
Msg-id 14139.1175567361@sss.pgh.pa.us
Whole thread Raw
In response to Re: Feature thought: idle in transaction timeout  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Feature thought: idle in transaction timeout  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Bruce Momjian wrote:
>> Added to TODO:
>> * Add idle_timeout GUC so locks are not held for log periods of time

> That should actually be transaction_idle_timeout. It is o.k. for us to 
> be IDLE... it is not o.k. for us to be IDLE in Transaction

Or "idle_in_transaction_timeout"?  Anyway I agree that using
"idle_timeout" for this is unwise.  We've been asked often enough for a
flat-out idle timeout (ie kill session after X seconds of no client
interaction), and while I disagree with the concept, someday we might
cave and implement it.  We should reserve the name for the behavior
that people would expect a parameter named like that to have.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Modifying TOAST thresholds
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Feature thought: idle in transaction timeout