Yes exactly, Geoff Winkless pointed that out too.
I thought I'd found a cause for the breaking connections, but I hadn't.
Thanks a lot for your help!
On Thu, Dec 15, 2022 at 3:48 PM Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Willy-Bas Loos <willybas@xxxxxxxxx> writes:
> It gives me a confirmation, but then when I SHOW the value, it gives me 0.
> wbloos=# set tcp_keepalives_idle=120;
> SET
> wbloos=# show tcp_keepalives_idle;
> tcp_keepalives_idle
> ---------------------
> 0
> (1 row)
That's the behavior I'd expect on a local (Unix-socket) connection
... you sure you're doing this from one of the problematic clients?
regards, tom lane
--
Willy-Bas Loos
