Re: Unexpected behavior after OOM errors

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unexpected behavior after OOM errors
Date: 2026-07-20 22:41:23
Message-ID: al6kEnBlIYH-518T@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 20, 2026 at 01:51:33PM +0200, Matthias van de Meent wrote:
> While the Assert is caused by other effects, it would still leave an
> incorrect rd_partcheck around in relcaches, so here's a patch that
> fixes that issue with rd_partcheckcxt. It also avoids leaking the
> context itself into the CacheMemoryContext when an OOM happens, so
> that's a neat addition.

Neater to not call AllocSetContextCreate() in the cache context this
way, indeed. That's better than what I have sent.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2026-07-21 00:38:48 Re: Row pattern recognition
Previous Message Tomas Vondra 2026-07-20 22:31:35 Re: hashjoins vs. Bloom filters (yet again)