[Question] strategy for multiple table alters

[mike-code]

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?

[tomkrouper]

Can you give more details? In our situation we tend to run migrations that are backwards compatible. If two tables need to be altered to make something work, we might migrate table 1, then table 2. After that developers would make changes to the code and If necessary, we'd migrate table 1 or 2 a second time to complete the process.