Re: [PATCH] nodeindexscan with reorder memory leak
Alexander Korotkov <aekorotkov@gmail.com>
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Aliaksandr Kalenik <akalenik@kontur.io>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2022-02-09T23:12:37Z
Lists: 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
Commits
-
Fix memory leak in IndexScan node with reordering
- 3f74daa8dfc6 15.0 landed
- 2e9033a54804 10.21 landed
- 0d554775bd04 11.16 landed
- 7a12a9e3cc97 12.11 landed
- ac2303aa0386 13.7 landed
- c76665edce3d 14.3 landed