Re: Release postmaster working memory context in slotsync worker - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Release postmaster working memory context in slotsync worker
Date
Msg-id CAHGQGwFWLN=-O3A7uBjmgYJt7Q9DMvn05C_aM7HMXg6DiSV_9Q@mail.gmail.com
Whole thread
In response to Re: Release postmaster working memory context in slotsync worker  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On Thu, Mar 19, 2026 at 5:16 PM Chao Li <li.evan.chao@gmail.com> wrote:
> Still, the current phrasing seems a bit too strong to me. Strictly speaking, the memory is already inherited at fork
time,so this is not making access impossible in an absolute sense. What this patch really does is remove the inherited
PostmasterContext,so the child no longer retains that postmaster-private data through that context. 
>
> Maybe we could phrase in some way like: "so that it no longer retains access to postmaster-private data through
PostmasterContext”.

Thanks for the review! I've pushed the patch.
Per your and Tiancheng's suggestions, I just used "prevent unintended use"
in the commit message.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PG 19 release notes and authors
Next
From: Daniel Gustafsson
Date:
Subject: Re: Environment variable to disable diffs file output