From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Keepalive |
Date: | 2024-06-15 16:17:04 |
Message-ID: | 2102D9CA-8FBD-49FE-821D-D74987442204@icloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Jun 14, 2024, at 1:47 PM, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Fri, 2024-06-14 at 11:22 -0400, Rui DeSousa wrote:
>> I have a very long running query that is not being terminated after a keep alive timeout event.
>> The situation is that the client drops from the network, the servers’ tcp/ip stack drops the
>> connection, and the Postgres query continues to run without a network connection.
>>
>> The given system is running on Linux and I’m being told this is expected behavior; however,
>> that is not has not been my experience. My preferred platform to run Postgres on is FreeBSD
>> and in cases like this the Postgres session is also terminated once the tcp/ip connection is
>> dropped by the kernel.
>
> That would surprise me.
>
> There is the parameter "client_connection_check_interval" exactly for that.
>
> Yours,
> Laurenz Albe
I retested the spinner() function on Linux with the client_connection_check_interval set and it now terminates the spinner() function.
Thanks!
Rui.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-06-15 23:25:27 | Re: Keepalive |
Previous Message | Achilleas Mantzios | 2024-06-15 15:56:26 | Re: Logical replication from PostgreSQL 10.23 to 16.3, last two big tables (getting synced) just keep growing |