]> source.dussan.org Git - sonarqube.git/commitdiff
projects / sonarqube.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 6304d93)
DOC-74 Strengthen wording of recommendation in upgrade guide doc (#6527)
authorTony B <56896165+TonyBgithub@users.noreply.github.com>
Mon, 29 Aug 2022 09:09:57 +0000 (11:09 +0200)
committersonartech <sonartech@sonarsource.com>
Mon, 29 Aug 2022 12:01:18 +0000 (12:01 +0000)
server/sonar-docs/src/pages/setup/upgrading.md patch | blob | history

diff --git a/server/sonar-docs/src/pages/setup/upgrading.md b/server/sonar-docs/src/pages/setup/upgrading.md
index cfe08245e2954e49edb81e1f1c0819876af00b0a..f084e689c919c1f2e7cd8c650df1f829bd07e76d 100644 (file)
--- 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:
 
Continuous Inspection: https://github.com/SonarSource/sonarqube