forked from MirrorHub/synapse
This happened if we encountered a stream ordering in `event_push_actions` that had more rows than the batch size of the delete, as If we don't delete any rows in an iteration then the next time round we get the exact same stream ordering and get stuck.
1 line
109 B
Text
1 line
109 B
Text
Fix bug where rows were not deleted from `event_push_actions` table on large servers. Introduced in v1.62.0.
|