| From: | Mats Kindahl <mats(at)timescale(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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-02-06 15:50:24 |
| Message-ID: | CA+144253kLtpL4iDaGK4z0yZ_2kd7KJktqEPMaw8sLze7L+ceg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 6, 2023 at 8:37 AM Mats Kindahl <mats(at)timescale(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-02-06 15:50:30 | Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off |
| Previous Message | Alvaro Herrera | 2023-02-06 15:43:00 | Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off |