Re: Questions/Observations related to Gist vacuum
Dilip Kumar <dilipbalaut@gmail.com>
From: Dilip Kumar <dilipbalaut@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>,
Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-10-17T13:02:31Z
Lists: pgsql-hackers
On Thu, 17 Oct 2019, 14:59 Amit Kapila, <amit.kapila16@gmail.com> wrote: > On Thu, Oct 17, 2019 at 1:47 PM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > > > On Thu, Oct 17, 2019 at 12:27 PM Heikki Linnakangas <hlinnaka@iki.fi> > wrote: > > > > > > On 17/10/2019 05:31, Amit Kapila wrote: > > > > > > > > The patch looks good to me. I have slightly modified the comments > and > > > > removed unnecessary initialization. > > > > > > > > Heikki, are you fine me committing and backpatching this to 12? Let > > > > me know if you have a different idea to fix. > > > > > > Thanks! Looks good to me. Did either of you test it, though, with a > > > multi-pass vacuum? > > > > From my side, I have tested it with the multi-pass vacuum using the > > gist index and after the fix, it's using expected memory context. > > > > I have also verified that, but I think what additionally we can test > here is that without the patch it will leak the memory in > TopTransactionContext (CurrentMemoryContext), but after patch it > shouldn't leak it during multi-pass vacuum. > > Make sense to me, I will test that by tomorrow.
Commits
-
Delete empty pages in each pass during GIST VACUUM.
- 4e514c6180fb 13.0 landed
-
Fix memory leak introduced in commit 7df159a620.
- 62f4dd3796da 12.1 landed
- 70a6c37d524c 13.0 landed
-
Delete empty pages during GiST VACUUM.
- 7df159a620b7 12.0 cited