From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Willy-Bas Loos <willybas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: tcp keepalives not sent during long query |
Date: | 2022-12-15 11:37:21 |
Message-ID: | 28b6e16270ac2e2a3e0343d6faa9c5ace97f37b3.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2022-12-15 at 08:31 +0100, Willy-Bas Loos wrote:
> On Wed, Dec 14, 2022 at 6:38 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > It'd be worth doing
> >
> > show tcp_keepalives_idle;
>
> Wow, you're right! It's in the postgresql.conf but it isn't set when I reload the server
> A restart also doesn't do it and even doing SET tcp_keepalives_idle=120; doesn't work.
> 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)
One good way to debug this is
SELECT setting, source, sourcefile, sourceline
FROM pg_settings
WHERE name = 'tcp_keepalives_idle';
That will tell you from where you get the parameter value.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2022-12-15 12:24:09 | Re: tcp keepalives not sent during long query |
Previous Message | Willy-Bas Loos | 2022-12-15 07:48:36 | Re: tcp keepalives not sent during long query |