From df8d5def80fa3abcef563310aa93b22d70cf4d37 Mon Sep 17 00:00:00 2001 From: Tony B <56896165+TonyBgithub@users.noreply.github.com> Date: Mon, 29 Aug 2022 11:09:57 +0200 Subject: [PATCH] DOC-74 Strengthen wording of recommendation in upgrade guide doc (#6527) --- server/sonar-docs/src/pages/setup/upgrading.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md index cfe08245e29..f084e689c91 100644 --- a/server/sonar-docs/src/pages/setup/upgrading.md +++ b/server/sonar-docs/src/pages/setup/upgrading.md @@ -118,7 +118,7 @@ Starting with version 6.6, there's an additional step you may want to perform if ### Additional database maintenance -We recommend refreshing your database's statistics and rebuilding your database's indices once you've finished the technical upgrade, but before you reanalyze your projects. +Once you've finished a technical upgrade, you should refresh your database's statistics and rebuild your database's indices before starting SonarQube and reanalyzing your projects. For PostgreSQL, that means executing `VACUUM FULL`. According to the PostgreSQL documentation: -- 2.39.5