Re: parallel vacuum comments
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>
Date: 2021-11-30T06:00:28Z
Lists: pgsql-hackers
On Tue, Nov 30, 2021 at 11:03 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > On Mon, Nov 29, 2021 11:38 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > > > 2) > + /* Reinitialize the parallel context to relaunch parallel workers */ > + if (!pvs->first_time) > > It seems the ParallelVacuumState::first_time was not initialized before ? > Yeah, I also notice this while looking at the patch. One more thing it seems the patch has removed even the existing error callback from parallel_vacuum_main. I suggested that we can enhance or add a new one if required in a separate patch but let's keep the current one as it is. Can we think of splitting the patch in the following manner: (a) the patch to get rid of bitmap to represent whether particular index supports parallel vacuum and rename of functions (b) any other stuff to improve the current implementation, (c) move the parallel vacuum related code to a separate file? I think if we can split the patch, it will be easier to review and reduce the chances of introducing any bugs in this area. -- With Regards, Amit Kapila.
Commits
-
Move parallel vacuum code to vacuumparallel.c.
- 8e1fae193864 15.0 landed
-
Move index vacuum routines to vacuum.c.
- cc8b25712b5e 15.0 landed
-
Improve parallel vacuum implementation.
- 22bd3cbe0c28 15.0 landed
-
Fix parallel amvacuumcleanup safety bug.
- c59278a1aa5e 15.0 landed
- f6162c020c88 14.1 landed
-
Simplify state managed by VACUUM.
- b4af70cb2103 14.0 cited