| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: idle_in_transaction_timeout |
| Date: | 2014-06-19 21:48:35 |
| Message-ID: | 53A35AB3.6010304@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/19/2014 02:44 PM, Kevin Grittner wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> Also, I really hope that nobody is setting this to 10s ...
>
> Well, we get to decide what the minimum allowed value is. What do
> you think that should be?
1s?
I don't think that setting it to 1s would ever be a good idea, but I
don't want to tie users' hands if they know better than I do. Also,
unless we use 1s granuarity, users can't set it to values like 45s,
which is more reasonable. I can't see any circumstance under which
sub-second values would ever make sense.
Now ... can we decrease CPU overhead (wakeups) if we only check once per
minute? If so, there's a good argument for making 1min the minimum.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2014-06-19 21:57:01 | Re: change alter user to be a true alias for alter role |
| Previous Message | Kevin Grittner | 2014-06-19 21:44:24 | Re: idle_in_transaction_timeout |