Re: parallel vacuum comments
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
Amit Kapila <amit.kapila16@gmail.com>
Date: 2021-11-03T02:53:09Z
Lists: pgsql-hackers
On Tue, Nov 2, 2021 at 7:35 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > It returns true in the above condition but it should return false > since the index doesn't support parallel index cleanup at all. It > seems that this bug was introduced by commit b4af70cb21 (therefore > exists only in PG14) which flipped the return values of this function > but missed one place. The index AMs that don't support parallel index > cleanup at all are affected by this bug. Among the supported index AM > in the core, hash indexes are affected but since they just return the > number of blocks during vacuumcleanup it would not become a serious > consequence. > > I've attached a patch to fix it. I pushed your fix just now. Thanks -- Peter Geoghegan
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