diff options
| author | michaelbirnstiehl <michael.birnstiehl@sonarsource.com> | 2021-01-27 10:02:13 -0600 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2021-01-27 20:07:39 +0000 |
| commit | f1093ddc3813076d0ee2108fce213423f4b1169d (patch) | |
| tree | 1447be9109cc657d35de5402d63808f81943a212 | |
| parent | bc558d75337b2dc52ecce2c96868f97554c4a037 (diff) | |
| download | sonarqube-f1093ddc3813076d0ee2108fce213423f4b1169d.tar.gz sonarqube-f1093ddc3813076d0ee2108fce213423f4b1169d.zip | |
DOCS Clarify the server upgrade Additional Database Maintenance section
| -rw-r--r-- | server/sonar-docs/src/pages/setup/upgrading.md | 2 |
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 0916c1bad43..e49cb31d30a 100644 --- a/server/sonar-docs/src/pages/setup/upgrading.md +++ b/server/sonar-docs/src/pages/setup/upgrading.md @@ -94,7 +94,7 @@ Starting with version 6.6, there's an additional step you may want to perform if ### Additional Database Maintenance -Refreshing your database's statistics and rebuilding your database's indices are recommended once the technical upgrade is done (just before the very last step). +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. For PostgreSQL, that means executing `VACUUM FULL`. According to the PostgreSQL documentation: |