Re: Crash during backend start when low on memory - Mailing list pgsql-bugs

From Mats Kindahl
Subject Re: Crash during backend start when low on memory
Date
Msg-id CA+144253kLtpL4iDaGK4z0yZ_2kd7KJktqEPMaw8sLze7L+ceg@mail.gmail.com
Whole thread Raw
In response to Re: Crash during backend start when low on memory  (Mats Kindahl <mats@timescale.com>)
List pgsql-bugs


On Mon, Feb 6, 2023 at 8:37 AM Mats Kindahl <mats@timescale.com> wrote:

I can remove the PG_TRY() and use ereport(LOG, ...) + ExitPostmaster if it feels like a safer path for incorporating a bug fix, but note that there is still a risk that the backend will tear down the postmaster. For example, allocating memory for a memory context can fail, or throwing another error inside the backend startup can also fail, so I think that there will be more work to do after this.

Not ExitPostmaster, of course, but some proc_exit call for the backend and returning status code for the postmaster.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
Next
From: Tom Lane
Date:
Subject: Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off