MIME-Version: 1.0
References: 
 <CAHGQGwHO05JaUpgKF8FBDmPdBUJsK22axRRcgmAUc2Jyi8OK8g@mail.gmail.com>
 <ukpuo66v3k5z5cpwfbofa3zwdgdb53thbxemgqvtsnf7gdf5ew@ixgj5hs4bwu6>
 <986903.1772215127@sss.pgh.pa.us>
 <CAHGQGwFu0tam9i2UxRHY+mrB-0YZVfWZPheKYy5V2KfB-WxuGQ@mail.gmail.com>
 <643f3b18.fedae.19d012e5009.Coremail.getiancheng_2012@163.com>
 <1D1EA490-4E6C-4AB2-8C1A-D02D26C23DE0@gmail.com>
In-Reply-To: <1D1EA490-4E6C-4AB2-8C1A-D02D26C23DE0@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
Date: Mon, 6 Apr 2026 23:09:49 +0900
Message-ID: 
 <CAHGQGwFWLN=-O3A7uBjmgYJt7Q9DMvn05C_aM7HMXg6DiSV_9Q@mail.gmail.com>
Subject: Re: Release postmaster working memory context in slotsync worker
To: Chao Li <li.evan.chao@gmail.com>
Cc: getiancheng <getiancheng_2012@163.com>, Tom Lane <tgl@sss.pgh.pa.us>,
	Andres Freund <andres@anarazel.de>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAHGQGwFWLN%3D-O3A7uBjmgYJt7Q9DMvn05C_aM7HMXg6DiSV_9Q%40mail.gmail.com>
Precedence: bulk

On Thu, Mar 19, 2026 at 5:16=E2=80=AFPM Chao Li <li.evan.chao@gmail.com> wr=
ote:
> Still, the current phrasing seems a bit too strong to me. Strictly speaki=
ng, the memory is already inherited at fork time, so this is not making acc=
ess impossible in an absolute sense. What this patch really does is remove =
the inherited PostmasterContext, so the child no longer retains that postma=
ster-private data through that context.
>
> Maybe we could phrase in some way like: "so that it no longer retains acc=
ess to postmaster-private data through PostmasterContext=E2=80=9D.

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,

--=20
Fujii Masao