Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nJm0x-00046P-47
	for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Feb 2022 00:48:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1nJm0v-0001yU-Rk
	for pgsql-bugs@arkaria.postgresql.org; Tue, 15 Feb 2022 00:48:17 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nJm0v-0001yL-Iv
	for pgsql-bugs@lists.postgresql.org; Tue, 15 Feb 2022 00:48:17 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nJm0s-0007TS-Hf
	for pgsql-bugs@lists.postgresql.org; Tue, 15 Feb 2022 00:48:17 +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 21F0m0HS2966712;
	Mon, 14 Feb 2022 19:48:00 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Daniel Gustafsson <daniel@yesql.se>,
 Thomas Munro <thomas.munro@gmail.com>,
        byavuz81@gmail.com,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>,
        Heikki Linnakangas <heikki.linnakangas@iki.fi>,
        Michael Paquier <michael@paquier.xyz>
Subject: Re: BUG #17391: While using --with-ssl=openssl and
 PG_TEST_EXTRA='ssl' options, SSL tests fail on OpenBSD 7.0
In-reply-to: <20220215004143.dlzsn72oqsmqa7uw@alap3.anarazel.de>
References: <C112C400-2CB5-4DCA-A699-00DC0333B665@yesql.se>
 <1537890.1644462214@sss.pgh.pa.us> <1952254.1644540297@sss.pgh.pa.us>
 <20220211011025.ek7exh6owpzjyudn@alap3.anarazel.de>
 <1955929.1644542728@sss.pgh.pa.us>
 <20220211015455.mkl6cvstttp5zfco@alap3.anarazel.de>
 <1959196.1644544971@sss.pgh.pa.us> <2077573.1644599439@sss.pgh.pa.us>
 <2187263.1644616494@sss.pgh.pa.us> <2458773.1644702998@sss.pgh.pa.us>
 <20220215004143.dlzsn72oqsmqa7uw@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Mon, 14 Feb 2022 16:41:43 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2966710.1644886080.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 14 Feb 2022 19:48:00 -0500
Message-ID: <2966711.1644886080@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/2966711.1644886080%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> I was just writing a test to verify that the slot / stats bug you just
> encountered is / stays fixed. I ended up doing it in isolationtester, be=
cause
> that was the easiest to get reliable. When terminating an isolationteste=
r
> connection, I see the FATAL twice in isolationtester output:

Yeah, see

https://www.postgresql.org/message-id/flat/ab4288f8-be5c-57fb-2400-e3e857f=
53e46%40enterprisedb.com

I haven't thought of a way to get rid of that that I like.
(There's a cleanup proposal in that thread that I've not
yet implemented, but it won't do anything for connection-loss
cases, I think.)

			regards, tom lane