public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Erik Dobák <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
Date: Tue, 15 Jul 2025 14:00:21 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwbENYBRre_Yo+jhtx+56b0W--AANjgJp1j-Ax9xUfAMxQ@mail.gmail.com>
References: <[email protected]>
	<CAKFQuwb4en2gPyGep4TghVeqitxBPsgiQAG5AZJ4yikBgUzooQ@mail.gmail.com>
	<CAH7-e5tbkVLKeaCEqv-_eL9D9Ppikvq-bmjviKVG6-ukkU7pXQ@mail.gmail.com>
	<[email protected]>
	<CAKFQuwbENYBRre_Yo+jhtx+56b0W--AANjgJp1j-Ax9xUfAMxQ@mail.gmail.com>

"David G. Johnston" <[email protected]> writes:
> The observed behavior of the server seems like a bug no matter how
> well-coded or not the software trying to make the connecting is.  The
> server should be able to close and disallow clients no matter what they are
> doing.

We will SIGKILL recalcitrant children during an "immediate" shutdown.
"Fast" shutdown is not defined to do that, and should not do so
because it'd imply having to do an unclean restart later.

I just tested logical replication both ways between current master and
v14 branch tip, and in either case the publishing server stops pretty
much instantaneously after "pg_ctl stop -m fast".  So I don't see
anything broken about our code, and I remain of the opinion that Qlik
is probably at fault.

			regards, tom lane

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox