Re: client_connection_check_interval default value - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: client_connection_check_interval default value
Date
Msg-id CAOYmi+=UXHJ2mmY3SXPFAV-79QcSCxM-4015te4Ka-5L_ewsow@mail.gmail.com
Whole thread Raw
In response to Re: client_connection_check_interval default value  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: client_connection_check_interval default value
List pgsql-hackers
On Thu, Feb 5, 2026 at 4:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think enabling it by default is a nonstarter, because it changes
> behavior in a significant way.  Specifically, it's always been the
> case that if the client disconnects during a non-SELECT query (or
> anything that doesn't produce output), the backend would complete that
> query before ending the session.

Ha, I hadn't even thought about the possibility of fire-and-forget...

> I think it's very likely that there
> are users depending on that behavior.

From a quick search, yeah, probably:

    https://dba.stackexchange.com/questions/247206/will-query-continue-to-run-even-after-network-times-out

--Jacob



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unfortunate pushing down of expressions below sort
Next
From: Masahiko Sawada
Date:
Subject: Re: pg_upgrade: optimize replication slot caught-up check