Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry
Date
Msg-id arRmqBEj9n0w3qCc@paquier.xyz
Whole thread
In response to Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry  (Grigorev Jurij <ju.grigorev@ftdata.ru>)
Responses Re: DSA_ALLOC_NO_OOM vs dsm_create ERROR leaving a half-initialized pgstats hash entry
List pgsql-hackers
On Thu, Sep 17, 2026 at 08:35:15AM +0000, Grigorev Jurij wrote:
> The two changes touch separate parts of pgstat_shmem.c, so the current
> HEAD patch should apply cleanly on top of the defensive change.  I do
> not expect any conflicts, but I will rebase and resend it if needed.

I have put my head down on this patch.  There was a lot of prose in
it, so I have spent time refining and making the whole shorter.
Another thing was some of the existing prose that got deleted, like
the comments at the top of "generation" and "refcount" when
initializing a new entry.

Cleaned up all that, and applied on HEAD.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: PG19: two RI fast-path issues found while testing the batching revert
Next
From: Etsuro Fujita
Date:
Subject: Re: Several issues with postgres_fdw stats import