From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rui DeSousa <rui.desousa@icloud.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Keepalive
In-reply-to: <161042FE-FC86-456B-A8E1-AED38AE01820@icloud.com>
References: <161042FE-FC86-456B-A8E1-AED38AE01820@icloud.com>
Comments: In-reply-to Rui DeSousa <rui.desousa@icloud.com>
	message dated "Fri, 14 Jun 2024 11:22:06 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2300377.1718378913.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 14 Jun 2024 11:28:33 -0400
Message-ID: <2300378.1718378913@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2300378.1718378913%40sss.pgh.pa.us>
Precedence: bulk

Rui DeSousa <rui.desousa@icloud.com> writes:
> I have a very long running query that is not being terminated after a ke=
ep alive timeout event.  The situation is that the client drops from the n=
etwork, the servers=E2=80=99 tcp/ip stack drops the connection, and the Po=
stgres query continues to run without a network connection.  =


> The given system is running on Linux and I=E2=80=99m being told this is =
expected behavior; however, that is not has not been my experience.  My pr=
eferred 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.

Really?

I would expect the query to keep running until the backend tries to
perform some I/O to the client.  How quickly that happens would depend
a great deal on the details of the query, but not on which OS you're
running on.

			regards, tom lane