From 9a3d41a26fbb00c67b1ac00306b21ab83f171e08 Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Mon, 19 Jul 2021 17:06:47 -0700 Subject: [PATCH] vacuumdb: Correct comment about --force-index-cleanup. Commit 3499df0d added a comment that incorrectly suggested that --force-index-cleanup did not appear in the same major version as the similar --no-index-cleanup option. In fact, both options are new to PostgreSQL 14. Backpatch: 14-, where both options were introduced. --- src/bin/scripts/vacuumdb.c | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/src/bin/scripts/vacuumdb.c b/src/bin/scripts/vacuumdb.c index 61974baa78..a85919c5c1 100644 --- a/src/bin/scripts/vacuumdb.c +++ b/src/bin/scripts/vacuumdb.c @@ -916,14 +916,7 @@ prepare_vacuum_command(PQExpBuffer sql, int serverVersion, } if (vacopts->force_index_cleanup) { - /* - * "INDEX_CLEANUP TRUE" has been supported since v12. - * - * Though --force-index-cleanup was added to vacuumdb in v14, - * the "INDEX_CLEANUP TRUE" server/VACUUM behavior has never - * changed. No reason not to support --force-index-cleanup on - * v12+. - */ + /* "INDEX_CLEANUP TRUE" has been supported since v12 */ Assert(serverVersion >= 120000); Assert(!vacopts->no_index_cleanup); appendPQExpBuffer(sql, "%sINDEX_CLEANUP TRUE", sep);