maxmustermann/synapse
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix vacuum instructions for sqlite

Browse source
This commit is contained in:
Brendan Abolivier 2020-01-03 13:51:59 +01:00
parent 51b8a21f0c
commit b7dec300b7
No known key found for this signature in database
GPG key ID: 1E015C145F1916CD
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/message_retention_policies.md
View file

@ -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. 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 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 operating system, the server admin needs to run `VACUUM FULL;` (or
database (see the related `VACUUM;` for SQLite databases) on Synapse's database (see the related
[PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-vacuum.html)). [PostgreSQL documentation](https://www.postgresql.org/docs/current/sql-vacuum.html)).