Re: [PATCH] nodeindexscan with reorder memory leak

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Aliaksandr Kalenik <akalenik(at)kontur(dot)io>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: [PATCH] nodeindexscan with reorder memory leak
Date: 2022-02-09 23:12:37
Message-ID: CAPpHfduLxM-tbmb+FqfNQrbgaUuLS1uKMZyeFTTv78jPfpD+BA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 10, 2022 at 1:19 AM Aliaksandr Kalenik <akalenik(at)kontur(dot)io> wrote:
> On Mon, Feb 7, 2022 at 11:20 PM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> > Regarding the memory leak, could you add a corresponding regression
> > test to the patch (probably similar to Tom's query upthread)?
>
> Yes, added similar to Tom's query but with polygons instead of circles.

I've rechecked that the now patched code branch is covered by
regression tests. I think the memory leak issue is independent of the
computational errors we've observed.

So, I'm going to push and backpatch this if no objections.

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-02-09 23:14:26 catalog access with reset GUCs during parallel worker startup
Previous Message Andres Freund 2022-02-09 23:11:29 Re: wrong fds used for refilenodes after pg_upgrade relfilenode changes