Uncertain redo‑log flush status and upgrade consistency after interrupted mysql_upgrade
When a mysql_upgrade operation is terminated unexpectedly, it is unclear whether InnoDB’s redo‑log entries have been fully flushed before crash‑recovery begins. The upgrade utility may consider partially upgraded tables as still requiring changes, and foreign‑key constraints remain enabled, creating ambiguity about data integrity. How can we verify that all