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

From Michael Paquier
Subject Re: Unexpected behavior after OOM errors
Date
Msg-id al3GMfsYHn1BCgkM@paquier.xyz
Whole thread
List pgsql-hackers
On Sun, Jul 19, 2026 at 02:16:47PM +0200, Alex Masterov wrote:
> The patch looks correct to me. Deleting the hash slot before raising the
> error is exactly the right cleanup, and MCXT_ALLOC_NO_OOM is the cleanest
> way to get there.

Thanks for looking.  Applied the portion touching
pgstat_get_entry_ref_cached() as of 16ebc196d892, for now.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
Next
From: Chao Li
Date:
Subject: Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows