Re: Memory leak in incremental sort re-scan - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory leak in incremental sort re-scan
Date
Msg-id 2275724.1686861393@sss.pgh.pa.us
Whole thread Raw
In response to Re: Memory leak in incremental sort re-scan  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: Memory leak in incremental sort re-scan
List pgsql-hackers
Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
> On 6/15/23 22:11, Tom Lane wrote:
>> I see zero leakage in that example after applying the attached quick
>> hack.  (It might be better to make the check in the caller, or to just
>> move the call to ExecInitIncrementalSort.)

> Thanks for looking. Are you planning to work on this and push the fix,
> or do you want me to finish this up?

I'm happy to let you take it -- got lots of other stuff on my plate.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Memory leak in incremental sort re-scan
Next
From: "Joel Jacobson"
Date:
Subject: Re: Do we want a hashset type?