diff options
| author | Brendan Abolivier <babolivier@matrix.org> | 2020-02-12 20:12:20 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-12 20:12:20 +0000 |
| commit | 6cd34da8b1138715d152539eacff653f6fdeb3b2 (patch) | |
| tree | 0fd18c26cfc8669466f8507080513a9479080bea /docs/message_retention_policies.md | |
| parent | Return a 404 for admin api user lookup if user not found (#6901) (diff) | |
| parent | Rephrase (diff) | |
| download | synapse-6cd34da8b1138715d152539eacff653f6fdeb3b2.tar.xz | |
Merge pull request #6891 from matrix-org/babolivier/retention-doc-amend
Spell out that the last event sent to a room won't be deleted by a purge
Diffstat (limited to 'docs/message_retention_policies.md')
| -rw-r--r-- | docs/message_retention_policies.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md index 4300809dfe..1dd60bdad9 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 |