Bug #84485 | Drop table crashes if innodb_force_recovery > 4 | ||
---|---|---|---|
Submitted: | 12 Jan 2017 12:24 | Modified: | 3 Feb 2017 19:15 |
Reporter: | Thirunarayanan Balathandayuthapani | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.7.15 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[12 Jan 2017 12:24]
Thirunarayanan Balathandayuthapani
[3 Feb 2017 19:15]
Daniel Price
Posted by developer: Fixed as of the upcoming 5.7.18, 8.0.1 release, and here's the changelog entry: A DROP TABLE operation raised an assertion on a server with an innodb_force_recovery setting of 5 or 6. DROP TABLE is no longer permitted with these innodb_force_recovery settings.