summary refs log tree commit diff
path: root/docs
diff options
context:
space:
mode:
authorRichard van der Hoff <github@rvanderhoff.org.uk>2017-10-16 10:43:22 +0100
committerGitHub <noreply@github.com>2017-10-16 10:43:22 +0100
commite5048169777b6004cd3e16517b7855d41033a4c1 (patch)
tree06f469795c7985f15a478b7e3373c100c1435dd5 /docs
parentBump version and changelog (diff)
parentmake it absolutely clear that Purge History API does not remove all traces of... (diff)
downloadsynapse-e5048169777b6004cd3e16517b7855d41033a4c1.tar.xz
Merge pull request #2540 from 4nd3r/patch-1
make it absolutely clear that purge doesn't remove everything
Diffstat (limited to 'docs')
-rw-r--r--docs/admin_api/purge_history_api.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/admin_api/purge_history_api.rst b/docs/admin_api/purge_history_api.rst
index 986efe40f9..08b3306366 100644
--- a/docs/admin_api/purge_history_api.rst
+++ b/docs/admin_api/purge_history_api.rst
@@ -4,6 +4,8 @@ Purge History API
 The purge history API allows server admins to purge historic events from their
 database, reclaiming disk space.
 
+**NB!** This will not delete local events (locally sent messages content etc) from the database, but will remove lots of the metadata about them and does dramatically reduce the on disk space usage
+
 Depending on the amount of history being purged a call to the API may take
 several minutes or longer. During this period users will not be able to
 paginate further back in the room from the point being purged from.