public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tomas Vondra <[email protected]>
To: Tom Lane <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: Memory leak in incremental sort re-scan
Date: Fri, 16 Jun 2023 00:34:54 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>



On 6/15/23 22:36, Tom Lane wrote:
> Tomas Vondra <[email protected]> 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.
> 

OK, will do.

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Memory leak in incremental sort re-scan
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox