diff --git a/changelog.d/6891.doc b/changelog.d/6891.doc new file mode 100644 index 0000000000000000000000000000000000000000..2f46c385b7ca91967c6253845806ef6c6a12847b --- /dev/null +++ b/changelog.d/6891.doc @@ -0,0 +1 @@ +Spell out that the last event sent to a room won't be deleted by a purge. diff --git a/docs/admin_api/purge_history_api.rst b/docs/admin_api/purge_history_api.rst index f7be226fd983d8f4646e4f8524395034436b073d..e2a620c54f8e390841b4249efc67bf9eda5a5ce5 100644 --- a/docs/admin_api/purge_history_api.rst +++ b/docs/admin_api/purge_history_api.rst @@ -8,6 +8,9 @@ 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. +Note that Synapse requires at least one message in each room, so it will never +delete the last message in a room. + The API is: ``POST /_synapse/admin/v1/purge_history/<room_id>[/<event_id>]`` diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md index 4300809dfe20845ae2d94e22c46619264f164953..1dd60bdad9526d1228ead34083c2c42623a1369f 100644 --- a/docs/message_retention_policies.md +++ b/docs/message_retention_policies.md @@ -42,6 +42,10 @@ purged according to its room's policy, then the receiving server will process and store that event until it's picked up by the next purge job, though it will always hide it from clients. +Synapse requires at least one message in each room, so it will never +delete the last message in a room. It will, however, hide it from +clients. + ## Server configuration