Re: Unexpected behavior after OOM errors

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alex Masterov <amasterov(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unexpected behavior after OOM errors
Date: 2026-07-20 06:54:41
Message-ID: al3GMfsYHn1BCgkM@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-07-20 06:59:51 Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
Previous Message Peter Eisentraut 2026-07-20 06:53:20 Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows