Commit 9a3d41a2 authored by Peter Geoghegan's avatar Peter Geoghegan

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.
parent 1e875138
...@@ -916,14 +916,7 @@ prepare_vacuum_command(PQExpBuffer sql, int serverVersion, ...@@ -916,14 +916,7 @@ prepare_vacuum_command(PQExpBuffer sql, int serverVersion,
} }
if (vacopts->force_index_cleanup) if (vacopts->force_index_cleanup)
{ {
/* /* "INDEX_CLEANUP TRUE" has been supported since v12 */
* "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+.
*/
Assert(serverVersion >= 120000); Assert(serverVersion >= 120000);
Assert(!vacopts->no_index_cleanup); Assert(!vacopts->no_index_cleanup);
appendPQExpBuffer(sql, "%sINDEX_CLEANUP TRUE", sep); appendPQExpBuffer(sql, "%sINDEX_CLEANUP TRUE", sep);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment