Before the successful renaming, a session accessed the ghost table, w… by abaowhy · Pull Request #1536 · github/gh-ost
…hich had already unlocked the original table. There is a very small probability that other sessions dml operations on the original table will occur, and this dml operation will appear in the original table after renaming, resulting in data loss.
dbking added 3 commits
April 30, 2025 09:36
thenam153 pushed a commit to thenam153/gh-ost that referenced this pull request
Jan 11, 2026This was referenced
Jan 16, 2026meiji163 added a commit that referenced this pull request
Jan 16, 2026
Since #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.
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