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 1pHXMH-0004ue-8c
	for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Jan 2023 21:49:37 +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 1pHXMF-00059B-UH
	for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Jan 2023 21:49:35 +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 1pHXMF-000592-MO
	for pgsql-bugs@lists.postgresql.org; Mon, 16 Jan 2023 21:49:35 +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 1pHXMD-0004S6-L0
	for pgsql-bugs@lists.postgresql.org; Mon, 16 Jan 2023 21:49:35 +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 30GLnUvl2100307;
	Mon, 16 Jan 2023 16:49:30 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mats Kindahl <mats@timescale.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, daniel@yesql.se,
        pgsql-bugs@lists.postgresql.org
Subject: Re: Crash during backend start when low on memory
In-reply-to: 
 <CA+14427pjo8-V2z+Rv5S6JL2-1JXzhQ0t_FkBaEx13_H7sPLdg@mail.gmail.com>
References: <20230113115352.sbuv5egpjyoxn52i@alvherre.pgsql>
 <1676515.1673622084@sss.pgh.pa.us>
 <CA+14426M6j-YrkNLu9Hsjerbh3nXaz1gQ-Di+L+EaDoZtkdMVg@mail.gmail.com>
 <1987527.1673902723@sss.pgh.pa.us>
 <CA+14427pjo8-V2z+Rv5S6JL2-1JXzhQ0t_FkBaEx13_H7sPLdg@mail.gmail.com>
Comments: In-reply-to Mats Kindahl <mats@timescale.com>
	message dated "Mon, 16 Jan 2023 22:10:10 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2100305.1673905770.1@sss.pgh.pa.us>
Date: Mon, 16 Jan 2023 16:49:30 -0500
Message-ID: <2100306.1673905770@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/2100306.1673905770%40sss.pgh.pa.us>
Precedence: bulk

Mats Kindahl <mats@timescale.com> writes:
> On Mon, Jan 16, 2023 at 9:58 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> There are no PG_TRY blocks in the postmaster, and certainly no recovery.

> I added one in the patch.

That's VERY unlikely to get accepted.

			regards, tom lane