Skip to content

Conversation

@grodowski
Copy link
Member

meiji163 and others added 5 commits November 24, 2025 07:04
This PR introduces revertible migrations, following the approach suggested by @jonahberquist. In case a migration causes production impact after the cut-over, it can be reverted quickly while preserving the writes that happened after the cut-over.

When gh-ost is invoked with the --checkpoint flag and the migration completes, the migration can be reverted by invoking gh-ost again with the --revert flag and the --old-table flag specifying the name of the "old" table from the first migration e.g. _mytable_del. Also see docs/revert.md.
Since github#1536, performance_schema.metadata_locks is required to check the rename session holds the metadata lock on the migrated table during cut-over. On some setups such as Aurora RDS performance_schema is not enabled by default and it may be infeasible to enable.
This PR adds --skip-metadata-lock-check flag to skip the check in this case.
@grodowski grodowski merged commit e3de7d7 into master Jan 22, 2026
11 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants