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-hackers-owner+archive@lists.postgresql.org>)
	id 1nbR6h-0006LU-Lu
	for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Apr 2022 18:07:15 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1nbR6f-00084R-Fk
	for pgsql-hackers@arkaria.postgresql.org; Mon, 04 Apr 2022 18:07:13 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	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 1nbR6f-00084I-6n
	for pgsql-hackers@lists.postgresql.org; Mon, 04 Apr 2022 18:07:13 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1nbR6c-0006NE-W7
	for pgsql-hackers@postgresql.org; Mon, 04 Apr 2022 18:07:12 +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 234I76FG1925661;
	Mon, 4 Apr 2022 14:07:06 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <mark.dilger@enterprisedb.com>
cc: Thomas Munro <thomas.munro@gmail.com>,
        PostgreSQL-development <pgsql-hackers@postgresql.org>,
        Joshua Brindle <joshua.brindle@crunchydata.com>,
        Robert Haas <robertmhaas@gmail.com>,
        Andrew Dunstan <andrew@dunslane.net>, Jeff Davis <pgsql@j-davis.com>,
        Joe Conway <joe@crunchydata.com>
Subject: Re: New Object Access Type hooks
In-reply-to: <AACAF464-092B-4497-ADA2-AE1B122FAC6A@enterprisedb.com>
References: <47F87A0E-C0E5-43A6-89F6-D403F2B45175@enterprisedb.com> <CA+hUKG+LOza8iSLiv6ymn=0R8S0x-R7KaqZmYfY+_b_cubcDOg@mail.gmail.com> <17BD82D7-49AC-40C9-8204-E7ADD30321A0@enterprisedb.com> <1918971.1649091790@sss.pgh.pa.us> <1922986.1649094077@sss.pgh.pa.us> <1923706.1649094673@sss.pgh.pa.us> <AACAF464-092B-4497-ADA2-AE1B122FAC6A@enterprisedb.com>
Comments: In-reply-to Mark Dilger <mark.dilger@enterprisedb.com>
	message dated "Mon, 04 Apr 2022 10:56:11 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1925659.1649095626.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 04 Apr 2022 14:07:06 -0400
Message-ID: <1925660.1649095626@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/1925660.1649095626%40sss.pgh.pa.us>
Precedence: bulk

Mark Dilger <mark.dilger@enterprisedb.com> writes:
> The test logs are attached.

Server log looks as-expected:

2022-04-04 09:11:51.087 PDT [2084] 013_crash_restart.pl LOG:  statement: S=
ELECT pg_sleep(3600);
2022-04-04 09:11:51.094 PDT [2083] 013_crash_restart.pl WARNING:  terminat=
ing connection because of unexpected SIGQUIT signal
2022-04-04 09:11:51.095 PDT [2070] LOG:  server process (PID 2083) exited =
with exit code 2
2022-04-04 09:11:51.095 PDT [2070] DETAIL:  Failed process was running: IN=
SERT INTO alive VALUES($$in-progress-before-sigquit$$) RETURNING status;
2022-04-04 09:11:51.095 PDT [2070] LOG:  terminating any other active serv=
er processes

I was hoping to see regress_log_013_crash_restart, though.

			regards, tom lane