This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Migrate stream_ordering to a bigint #10264
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Fix a long-standing bug where Synapse would return errors after 2<sup>31</sup> events were handled by the server. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
synapse/storage/schema/main/delta/60/01recreate_stream_ordering.sql.postgres
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
/* Copyright 2021 The Matrix.org Foundation C.I.C | ||
* | ||
* Licensed under the Apache License, Version 2.0 (the "License"); | ||
* you may not use this file except in compliance with the License. | ||
* You may obtain a copy of the License at | ||
* | ||
* http://www.apache.org/licenses/LICENSE-2.0 | ||
* | ||
* Unless required by applicable law or agreed to in writing, software | ||
* distributed under the License is distributed on an "AS IS" BASIS, | ||
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ | ||
|
||
-- This migration handles the process of changing the type of `stream_ordering` to | ||
-- a BIGINT. | ||
-- | ||
-- Note that this is only a problem on postgres as sqlite only has one "integer" type | ||
-- which can cope with values up to 2^63. | ||
|
||
-- First add a new column to contain the bigger stream_ordering | ||
ALTER TABLE events ADD COLUMN stream_ordering2 BIGINT; | ||
|
||
-- Create a rule which will populate it for new rows. | ||
CREATE OR REPLACE RULE "populate_stream_ordering2" AS | ||
ON INSERT TO events | ||
DO UPDATE events SET stream_ordering2=NEW.stream_ordering WHERE stream_ordering=NEW.stream_ordering; | ||
|
||
-- Start a bg process to populate it for old events | ||
INSERT INTO background_updates (ordering, update_name, progress_json) VALUES | ||
(6001, 'populate_stream_ordering2', '{}'); | ||
|
||
-- ... and another to build an index on it | ||
INSERT INTO background_updates (ordering, update_name, progress_json, depends_on) VALUES | ||
(6001, 'index_stream_ordering2', '{}', 'populate_stream_ordering2'); | ||
|
||
-- ... and another to do the switcheroo | ||
INSERT INTO background_updates (ordering, update_name, progress_json, depends_on) VALUES | ||
(6001, 'replace_stream_ordering_column', '{}', 'index_stream_ordering2'); |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this an issue here? I'd expect setting batch_size to zero/negative anywhere is going to cause issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true. It's just defensive here.