| From: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: idle_in_transaction_timeout |
| Date: | 2014-06-23 20:40:49 |
| Message-ID: | CAKFQuwb5PC_=-bEDCsWX6TTCCQ8JqosqVn0eFA+XbqNzYZ821g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> > A long idle in transaction state pretty much always indicates a
> > problematic interaction with postgres.
>
> True. Which makes me wonder whether we shouldn't default this to
> something non-zero -- even if it is 5 or 10 days.
I guess it depends on how parental we want to be. But if we go that route
wouldn't a more harsh/in-your-face default make more sense? Something in
Minutes, not Days...say '5min'...
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/idle-in-transaction-timeout-tp5805859p5808473.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-06-23 20:51:55 | Re: pgaudit - an auditing extension for PostgreSQL |
| Previous Message | David G Johnston | 2014-06-23 20:34:01 | Re: idle_in_transaction_timeout |