Re: Memory leak in incremental sort re-scan

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Memory leak in incremental sort re-scan
Date: 2023-06-29 11:49:54
Message-ID: 1eeeebf37fda63cf0946e9b77e5bd6a8ac827615.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2023-06-16 at 00:34 +0200, Tomas Vondra wrote:
> On 6/15/23 22:36, Tom Lane wrote:
> > Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)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.
>
> OK, will do.

It would be cool if we could get that into the next minor release in August.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2023-06-29 12:21:34 Re: Incremental View Maintenance, take 2
Previous Message Ranier Vilela 2023-06-29 11:23:22 Re: POC, WIP: OR-clause support for indexes