Re: Backpatch for fix simplehash to preserve consistency in case of OOM

From: Andres Freund <andres(at)anarazel(dot)de>
To: Gilles Darold <gilles(at)darold(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Backpatch for fix simplehash to preserve consistency in case of OOM
Date: 2026-11-20 17:09:20
Message-ID: evlu5bjfo32rx4xrymklvdismyzuetl5pvupldm7zg2vy32xm3@bkqihll4qlzh
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-11-20 19:59:09 +0300, Gilles Darold wrote:
> I have experienced a PG 16.14 backend crashed with SIGSEGV during an
> out-of-memory episode. Analysis of the core dump shows that this is the bug
> fixed on master by commit b282fa88df ("simplehash: preserve consistency
> in case of OOM.", 2023-11-17). That commit is in v17 and later, but it was
> never back-patched to REL_16_STABLE. Here are the details of the commit
> message:

I think Jeff didn't backpatch it because the use where that he newly
introduced that could be problematic wasn't in 16:

Author: Jeff Davis <jdavis(at)postgresql(dot)org>
Branch: master Release: REL_17_BR [f26c2368d] 2023-11-14 17:53:30 -0800

Add cache for recomputeNamespacePath().

Can you provide a bit more detail about what you encountered?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-11-20 17:15:07 Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments
Previous Message Nathan Bossart 2026-11-20 17:03:04 Re: pg_restore fails on extracted tar archives with large objects