From: | "Tristan Partin" <tristan(at)neon(dot)tech> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Default client_connection_check_interval to 10s on supported systems |
Date: | 2023-06-16 22:16:59 |
Message-ID: | CTEF7Y787TF4.1IIA8X5IXWWQJ@gonk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri Jun 16, 2023 at 5:10 PM CDT, Tom Lane wrote:
> "Tristan Partin" <tristan(at)neon(dot)tech> writes:
> > I am proposing that the default value of
> > client_connection_check_interval be moved to a non-zero value on
> > systems where it is supported. I think it would be a nice quality of
> > life improvement.
>
> I doubt that we need this, and I *really* doubt that it's appropriate
> to use a timeout as short as 10s.
Sure. Like I said, 10s is just a number pulled from thin air. The
original patches on the mailing list had this as low as 1s.
> One reason not to try to enable it by default is exactly that the
> default behavior would then be platform-dependent. That's a
> documentation problem we could do without.
Totally fine with me if this is the reason for rejection. Just wanted to
put it out there for discussion since I don't think the original thread
covered the default value very much.
--
Tristan Partin
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Quan Zongliang | 2023-06-16 22:32:58 | Re: Incorrect estimation of HashJoin rows resulted from inaccurate small table statistics |
Previous Message | Tristan Partin | 2023-06-16 22:11:59 | Re: [PATCH] Missing dep on Catalog.pm in meson rules |