aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2021-07-19 17:06:47 -0700
committerPeter Geoghegan <pg@bowt.ie>2021-07-19 17:06:47 -0700
commit9a3d41a26fbb00c67b1ac00306b21ab83f171e08 (patch)
tree8f97a8f6a7233031cb70bd9b0ba1ff2c59b71d47
parent1e8751380836056fdf546433dcf0328bc18c9313 (diff)
downloadpostgresql-9a3d41a26fbb00c67b1ac00306b21ab83f171e08.tar.gz
postgresql-9a3d41a26fbb00c67b1ac00306b21ab83f171e08.zip
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.
-rw-r--r--src/bin/scripts/vacuumdb.c9
1 files changed, 1 insertions, 8 deletions
diff --git a/src/bin/scripts/vacuumdb.c b/src/bin/scripts/vacuumdb.c
index 61974baa780..a85919c5c19 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);