Fix incredubly slow back pagination query
If a client didn't specify a from token when paginating backwards synapse would attempt to query the (global) maximum topological token. This a) doesn't make much sense since they're room specific and b) there are no indices that lets postgres do this efficiently.
Showing
- synapse/handlers/message.py 2 additions, 2 deletionssynapse/handlers/message.py
- synapse/handlers/room.py 5 additions, 2 deletionssynapse/handlers/room.py
- synapse/storage/stream.py 13 additions, 6 deletionssynapse/storage/stream.py
- synapse/streams/events.py 28 additions, 2 deletionssynapse/streams/events.py
Loading
Please register or sign in to comment