NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit28766c0

committed

vacuumdb: Correct comment about --force-index-cleanup.

Commit3499df0 added a comment that incorrectly suggested that--force-index-cleanup did not appear in the same major version as thesimilar --no-index-cleanup option. In fact, both options are new toPostgreSQL 14.Backpatch: 14-, where both options were introduced.

1 parent0c08856 commit28766c0Copy full SHA for 28766c0

File tree

1 file changed

-8

lines changed

src/bin/scripts
- vacuumdb.c

1 file changed

-8

lines changed

`‎src/bin/scripts/vacuumdb.c`

Lines changed: 1 addition & 8 deletions

Original file line number	Diff line number	Diff line change
`@@ -916,14 +916,7 @@ prepare_vacuum_command(PQExpBuffer sql, int serverVersion,`
`916`	`916`	`}`
`917`	`917`	`if (vacopts->force_index_cleanup)`
`918`	`918`	`{`
`919`		`-/*`
`920`		`- * "INDEX_CLEANUP TRUE" has been supported since v12.`
`921`		`- *`
`922`		`- * Though --force-index-cleanup was added to vacuumdb in v14,`
`923`		`- * the "INDEX_CLEANUP TRUE" server/VACUUM behavior has never`
`924`		`- * changed. No reason not to support --force-index-cleanup on`
`925`		`- * v12+.`
`926`		`- */`
	`919`	`+/* "INDEX_CLEANUP TRUE" has been supported since v12 */`
`927`	`920`	`Assert(serverVersion >=120000);`
`928`	`921`	`Assert(!vacopts->no_index_cleanup);`
`929`	`922`	`appendPQExpBuffer(sql,"%sINDEX_CLEANUP TRUE",sep);`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit28766c0

File tree

1 file changed

1 file changed

`‎src/bin/scripts/vacuumdb.c`

0 commit comments