Proposing using gh-ost for deleting old/specific data from mysql tab… #1621
+842
−4
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
to avoid deadlocks, be able to deal with big size table and be able to check deleted data before removal, I came to use gh-ost for this case added supporting a `WHERE` condition that allows only moving/copying the data that meets the condition to the new table
AdhamMGaber9
requested review from
meiji163,
rashiq and
timvaillancourt
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To avoid deadlocks, be able to deal with big size table and be able to check deleted data before removal, I came to use gh-ost for this case added supporting a
WHEREcondition that allows only moving/copying the data that meets the condition to the new tableRelated issue: #1620