summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrendan Abolivier <babolivier@matrix.org>2020-01-03 13:51:59 +0100
committerBrendan Abolivier <babolivier@matrix.org>2020-01-03 13:51:59 +0100
commitb7dec300b7419402a0d5fc00e34684b95618a7d9 (patch)
tree7c948fbf806ba82362ad1c4e4697b6680a255cbb
parentRename changelog (diff)
downloadsynapse-b7dec300b7419402a0d5fc00e34684b95618a7d9.tar.xz
Fix vacuum instructions for sqlite
-rw-r--r--docs/message_retention_policies.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md
index 78055b2f64..72f08fbb4c 100644
--- a/docs/message_retention_policies.md
+++ b/docs/message_retention_policies.md
@@ -185,7 +185,7 @@ host. However, even though the database engine won't free up the disk
 space, it will start writing new data into where the purged data was.
 
 If you want to reclaim the freed disk space anyway and return it to the
-operating system, the server admin needs to run `VACUUM FULL;` on the
-database (see the related
+operating system, the server admin needs to run `VACUUM FULL;` (or
+`VACUUM;` for SQLite databases) on Synapse's database (see the related
 [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-vacuum.html)).