Re: Crash during backend start when low on memory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mats Kindahl <mats(at)timescale(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, daniel(at)yesql(dot)se, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Crash during backend start when low on memory
Date: 2023-01-16 20:58:43
Message-ID: 1987527.1673902723@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Mats Kindahl <mats(at)timescale(dot)com> writes:
> On Fri, Jan 13, 2023 at 4:01 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, the BackendStartup change is 100% wrong; it is replacing
>> perfectly good code that recovers correctly with bad code that
>> will take down the postmaster (not a backend child!) on OOM.

> AFAICT, the error is caught by the caller (using PG_TRY), executes some
> cleanup code, and then continues executing, so it shouldn't take down the
> postmaster.

There are no PG_TRY blocks in the postmaster, and certainly no recovery.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Mats Kindahl 2023-01-16 21:10:10 Re: Crash during backend start when low on memory
Previous Message Mats Kindahl 2023-01-16 20:52:41 Re: Crash during backend start when low on memory