aboutsummaryrefslogtreecommitdiffstats
path: root/server/sonar-docs/src/pages/setup
diff options
context:
space:
mode:
authorTony B <56896165+TonyBgithub@users.noreply.github.com>2022-08-29 11:09:57 +0200
committersonartech <sonartech@sonarsource.com>2022-08-29 12:01:18 +0000
commitdf8d5def80fa3abcef563310aa93b22d70cf4d37 (patch)
tree6ed6bc3576a471aaac5e2e14c8def74b0fab99a7 /server/sonar-docs/src/pages/setup
parent6304d93991af2397eb8c5ab665a61ea93434030e (diff)
downloadsonarqube-df8d5def80fa3abcef563310aa93b22d70cf4d37.tar.gz
sonarqube-df8d5def80fa3abcef563310aa93b22d70cf4d37.zip
DOC-74 Strengthen wording of recommendation in upgrade guide doc (#6527)
Diffstat (limited to 'server/sonar-docs/src/pages/setup')
-rw-r--r--server/sonar-docs/src/pages/setup/upgrading.md2
1 files changed, 1 insertions, 1 deletions
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: