回复:BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset

Haiyang Li <mohen.lhy@alibaba-inc.com>

From: 李海洋(陌痕) <mohen.lhy@alibaba-inc.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: "feichanghong" <feichanghong@qq.com>, "ocean_li_996" <ocean_li_996@163.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-09-09T01:52:26Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Eliminate duplicative hashtempcxt in nodeSubplan.c.

  2. Fix memory leakage in nodeSubplan.c.

  3. Do execGrouping.c via expression eval machinery, take two.

  4. Fix potential failure when hashing the output of a subplan that produces

On 2025-09-08 20:46:10 Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Concretely, I'm thinking about the attached. 0001 is the same
> logic as in the v02 patch, but I felt we could make the code
> be shorter and prettier instead of longer and uglier. That’s
> meant for back-patch, and then 0002 is for master only.
Yeah, v04-0001 and v04-0002 look good for me. 
Thanks for refining the patch.
—
Thanks
Haiyang Li