Re: Unexpected behavior after OOM errors - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Unexpected behavior after OOM errors
Date
Msg-id ajZFM1XwbDpTQYZV@paquier.xyz
Whole thread
In response to Re: Unexpected behavior after OOM errors  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Unexpected behavior after OOM errors
Re: Unexpected behavior after OOM errors
List pgsql-hackers
On Fri, Jun 19, 2026 at 08:12:47PM +0900, Michael Paquier wrote:
> On Fri, Jun 19, 2026 at 09:18:03AM +0200, Matthias van de Meent wrote:
>> Ah, thanks for correcting me. I'm not sure why I had ERROR in mind,
>> but you're obviously correct. Your patch v2 LGTM.
>
> Cool, thanks.

And done that as well.  If we invent a new facility, I'd be curious to
see how this would apply here or to other parts of the backend.  And
perhaps not only for initialization steps?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Compile warnings under -DMEMORY_CONTEXT_CHECKING and no assertions
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Fix two incorrect code comments