Re: [PATCH] nodeindexscan with reorder memory leak - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: [PATCH] nodeindexscan with reorder memory leak
Date
Msg-id CAPpHfduLxM-tbmb+FqfNQrbgaUuLS1uKMZyeFTTv78jPfpD+BA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] nodeindexscan with reorder memory leak  (Aliaksandr Kalenik <akalenik@kontur.io>)
Responses Re: [PATCH] nodeindexscan with reorder memory leak
List pgsql-hackers
On Thu, Feb 10, 2022 at 1:19 AM Aliaksandr Kalenik <akalenik@kontur.io> wrote:
> On Mon, Feb 7, 2022 at 11:20 PM Alexander Korotkov <aekorotkov@gmail.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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: wrong fds used for refilenodes after pg_upgrade relfilenode changes
Next
From: Andres Freund
Date:
Subject: catalog access with reset GUCs during parallel worker startup