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 1rs1eh-004JUV-UG for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Apr 2024 14:32:00 +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 1rs1eg-002xxX-Hy for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Apr 2024 14:31:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rs1eg-002xxP-8Y for pgsql-hackers@lists.postgresql.org; Wed, 03 Apr 2024 14:31:58 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rs1ed-000R5h-SR for pgsql-hackers@postgresql.org; Wed, 03 Apr 2024 14:31:57 +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 433EVe1B2049576; Wed, 3 Apr 2024 10:31:40 -0400 From: Tom Lane To: Jelte Fennema-Nio cc: Robert Haas , Tristan Partin , Heikki Linnakangas , pgsql-hackers@postgresql.org, Shlok Kyal Subject: Re: psql not responding to SIGINT upon db reconnection In-reply-to: References: <1588058.1690220636@sss.pgh.pa.us> <5e28b89f-0033-4e42-8184-b71b731c1aa2@iki.fi> <9b3693b7-0bc3-430a-b43f-eae44e8a39b6@iki.fi> <032868e0-a530-4fc7-972c-af6f08950b7e@iki.fi> Comments: In-reply-to Jelte Fennema-Nio message dated "Wed, 03 Apr 2024 15:32:39 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2049573.1712154700.1@sss.pgh.pa.us> Date: Wed, 03 Apr 2024 10:31:40 -0400 Message-ID: <2049574.1712154700@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jelte Fennema-Nio writes: > Looking at the committed version of this patch, the pg_unreachable > calls seemed weird to me. 1 is actually incorrect, thus possibly > resulting in undefined behaviour. And for the other call an imho > better fix would be to remove the now 21 year unused enum variant, > instead of introducing its only reference in the whole codebase. If we do the latter, we will almost certainly get pushback from distros who check for library ABI breaks. I fear the comment suggesting that we could remove it someday is too optimistic. regards, tom lane