[Question] strategy for multiple table alters
Open
question
- Dominant language
- Go
- Stars
- 13.6k
- Forks
- 1.4k
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 4
Description
Imagine the migration alters two tables, but if I read the doc correctly gh-ost supports single table alteration. I understand that there's no "good way" of handling this kind of situation because even if you run migrations simultaneously (two instances of gh-ost), at some point you'll end up having one table migrated while the other one still in migration.
Do I assume correctly that the only right way here is just not allowing such migrations in the first place if you care about zero downtime?
Contributor guide
Assessment
This issue has not been assessed yet.