fix ordering of bg update (#10291)

this was a typo introduced in #10282. We don't want to end up doing the
`replace_stream_ordering_column` update after anything that comes up in
migration 60/03.
This commit is contained in:
Richard van der Hoff 2021-07-01 18:45:55 +01:00 committed by GitHub
parent e72c287418
commit 0aab50c772
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 1 deletions

1
changelog.d/10291.bugfix Normal file
View File

@ -0,0 +1 @@
Fix a long-standing bug where Synapse would return errors after 2<sup>31</sup> events were handled by the server.

View File

@ -42,4 +42,4 @@ INSERT INTO background_updates (ordering, update_name, progress_json, depends_on
-- ... and another to do the switcheroo -- ... and another to do the switcheroo
INSERT INTO background_updates (ordering, update_name, progress_json, depends_on) VALUES INSERT INTO background_updates (ordering, update_name, progress_json, depends_on) VALUES
(6003, 'replace_stream_ordering_column', '{}', 'index_stream_ordering2_ts'); (6001, 'replace_stream_ordering_column', '{}', 'index_stream_ordering2_ts');