| Bug #83241 | Find a way to list #sql... table left in data dictionary in case ALTER fails. | ||
|---|---|---|---|
| Submitted: | 3 Oct 2016 5:22 | Modified: | 22 Jun 2017 16:34 |
| Reporter: | Gopal Shankar | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: DDL | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
[22 Jun 2017 16:34]
Paul DuBois
Posted by developer: Fixed in 8.0.2. The SHOW TABLES statement now supports an optional EXTENDED keyword that causes statement output to list hidden tables created by failed ALTER TABLE statements. (These temporary tables have names beginning with #sql.)
Description: After .frm files are removed by introduction of data dictionary tables, there is following effect. In MySQL 5.7, if there was some issue during ALTER TABLE command processing and then temporary files '#sql...' created to hold new table definition were left on disk. MySQL users could just scan the data directory to find these tables named '#sql', to check if server has hit such a problem. The problem is that there is no way to find such problems in MySQL 8.0. Related bugs are: 24571427, 24580599, 24597852. How to repeat: na Suggested fix: This bug should handle, - How to list '#sql..' tables left in data dictionary tables ? How to clean them ? - How to differenciate '#sql...' tables created by CREATE TABLE commandand ALTER TABLE.