Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry

From: Grigorev Jurij <ju(dot)grigorev(at)ftdata(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry
Date: 2026-09-24 03:39:10
Message-ID: ee29f27c0c9f4520b3cf2135f7dc7a2b@localhost.localdomain
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Michael,

Thanks very much for taking the time to clean this up and commit it. I
reviewed d9de60c -- restoring the existing refcount and generation
comments was the right call, and the shorter wording still captures the
allocation-before-insert invariant. The final ordering and cleanup
paths look good to me.

Thanks,
Yuriy

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2026-09-24 03:42:34 RI fastpath misses checking EXECUTE on functions
Previous Message Chao Li 2026-09-24 03:09:05 Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)