Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubjx5-004dt4-5X for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 18:00:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ubjx3-004GFP-8I for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Jul 2025 18:00:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ubjx2-004GFH-Vv for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 18:00:25 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ubjx1-007Rd2-2u for pgsql-bugs@lists.postgresql.org; Tue, 15 Jul 2025 18:00:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 56FI0LIE936090; Tue, 15 Jul 2025 14:00:21 -0400 From: Tom Lane To: "David G. Johnston" cc: =?UTF-8?Q?Erik_Dob=C3=A1k?= , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #18985: fast shutdown does not close connections from qlik data gateway data movement aka. replicate In-reply-to: References: <18985-64431d78bcabae95@postgresql.org> <923969.1752595701@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Tue, 15 Jul 2025 09:27:36 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <936088.1752602421.1@sss.pgh.pa.us> Date: Tue, 15 Jul 2025 14:00:21 -0400 Message-ID: <936089.1752602421@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" 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