Fix possible action data loss in segmentation due to signed int32 overflow #21451
Conversation
This file contains hidden or 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
|
Makes sense, I can't think of any downside 👍 |
sgiehl
approved these changes
Oct 31, 2023
|
Thanks for your contribution @MichaelRoosz 🎉 |
caddoo
pushed a commit
that referenced
this pull request
Nov 5, 2023
caddoo
pushed a commit
that referenced
this pull request
Nov 5, 2023
caddoo
pushed a commit
that referenced
this pull request
Nov 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When idaction exceeds signed int32 max (2147483647) - the temp table in "createTempTableForStoringUsedActions()" cannot store the idactions anymore and thus still used log_action rows will get deleted.