diff options
| author | Erik Johnston <erikj@element.io> | 2024-05-29 13:19:10 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-29 12:19:10 +0000 |
| commit | 466f344547fc6bea2c43257dd65286380fbb512d (patch) | |
| tree | 40ba5abd666ac6584b7d7cbae3603a3898ce91c5 /debian/synapse_review_recent_signups.1 | |
| parent | Don't invalidate all `get_relations_for_event` on history purge (#17083) (diff) | |
| download | synapse-466f344547fc6bea2c43257dd65286380fbb512d.tar.xz | |
Move towards using `MultiWriterIdGenerator` everywhere (#17226)
There is a problem with `StreamIdGenerator` where it can go backwards over restarts when a stream ID is requested but then not inserted into the DB. This is problematic if we want to land #17215, and is generally a potential cause for all sorts of nastiness. Instead of trying to fix `StreamIdGenerator`, we may as well move to `MultiWriterIdGenerator` that does not suffer from this problem (the latest positions are stored in `stream_positions` table). This involves adding SQLite support to the class. This only changes id generators that were already using `MultiWriterIdGenerator` under postgres, a separate PR will move the rest of the uses of `StreamIdGenerator` over.
Diffstat (limited to 'debian/synapse_review_recent_signups.1')
0 files changed, 0 insertions, 0 deletions