-
Notifications
You must be signed in to change notification settings - Fork 190
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
Feature request: Drop old lhma_ tables #99
Comments
@sroysen as you bringing up the point, is there any way to know if those tables are still hot or not, so we can safely drop them without locking? Thanks |
@arthurnn I saw the note in the usage section of gem stating that But I don't have any use case for retaining the lhma table. Can we have another parameter to the |
I use this in my Rakefile:
I agree that this should not be an automatic step, but performed manually after everything is validated. |
Just dropping lhma tables might impact your availability, as at least on MySQL 5.x, and seemingly on some versions of MySQL 8.x as well, see: github/gh-ost#307 (comment) We built a Sidekiq job that implements this protocol:
|
Since LHM tasks are the ones creating lhma_ tables when renaming the old tables on an online schema change, it would be nice that the same code provides an option to drop those that were created 'n' days ago.
Something that could be run like:
The text was updated successfully, but these errors were encountered: