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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: feichanghong <feichanghong(at)qq(dot)com>
Cc: "李海洋(陌痕)" <mohen(dot)lhy(at)alibaba-inc(dot)com>, ocean_li_996 <ocean_li_996(at)163(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
Date: 2025-09-09 03:05:09
Message-ID: 1073615.1757387109@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

feichanghong <feichanghong(at)qq(dot)com> writes:
> For v04-0002, I checked the commit history, and before commit 133924e1,
> buildSubPlanHash was using ecxt_per_tuple_memory. It seems that the
> "Subplan HashTable Temp Context" was introduced in order to fix a certain bug.

It was a different ExprContext's ecxt_per_tuple_memory, though.
This one is owned locally by the TupleHashTable.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 李海洋 (陌痕) 2025-09-09 07:30:48 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
Previous Message feichanghong 2025-09-09 02:51:56 Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset