Horton

Re: Memory leak in incremental sort re-scan

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-hackers@lists.postgresql.org
Date: 2023-06-15T20:36:33Z
Lists: 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

Commits

  1. Fix memory leak in Incremental Sort rescans