-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix get_last_event_in_room_before_stream_ordering(...)
finding the wrong last event
#17295
Merged
MadLittleMods
merged 9 commits into
develop
from
madlittlemods/fix-and-tests-for-get_last_event_in_room_before_stream_ordering
Jun 13, 2024
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
87ad458
Fix `get_last_event_in_room_before_stream_ordering(...)` not finding …
MadLittleMods 431b31e
Add actual guranteed order for UNION
MadLittleMods d7f40ae
Try to better explain why
MadLittleMods a8056ae
Add changelog
MadLittleMods 3f317a9
We're actually using sub-query syntax so we can ORDER each query
MadLittleMods 54bdc0c
Fix invalid syntax
MadLittleMods 4d585b6
Merge branch 'develop' into madlittlemods/fix-and-tests-for-get_last_…
MadLittleMods d3ba660
Update wording
MadLittleMods 8a9cc2b
Merge branch 'develop' into madlittlemods/fix-and-tests-for-get_last_…
MadLittleMods 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 edge case in `/sync` returning the wrong the state when using sharded event persisters. |
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
Oops, something went wrong.
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.
Previously, the query would return rows in
stream_ordering
ascending order becauseUNION
does not preserve ordering of the operand queries.UNION
also behaves as a union +DISTINCT
whereasUNION ALL
is just the union behavior you're probably expecting.Before (ascending):
Since we don't need that
DISTINCT
behavior (because our sub-queries are mutually exclusive anyway and duplicates wouldn't matter anyway), we are now usingUNION ALL
which preserves the order of the operand queries (works correctly by itself in my testing) but may not preserve the order in all cases, with different indexes or partitioning or a parallel plan. So we add an extraORDER BY stream_ordering DESC
to the end to give us the actual guarantee.After (descending):
See https://dba.stackexchange.com/questions/316818/are-results-from-union-all-clauses-always-appended-in-order/316835#316835 for more info on the
UNION ALL
order guarantee.