Bug #97472 | TRUNCATE TABLE in init-file leaves an orphan .ibd | ||
---|---|---|---|
Submitted: | 4 Nov 2019 15:34 | Modified: | 1 Mar 2022 10:52 |
Reporter: | Andrew Garner | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0.18 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[4 Nov 2019 15:34]
Andrew Garner
[28 Nov 2019 18:06]
MySQL Verification Team
I cannot reproduce this outside of docker. Thanks for your report
[29 Apr 2020 20:35]
Andrew Garner
This seems like this was bug #30721214, perhaps. > InnoDB: DDL logging was not performed for SQL operations executed by the bootstrap thread using the init_file startup variable, causing files to be left behind that should have been removed during a post-DDL stage. (Bug #30721214) Not repeatable on 8.0.20. Thanks?
[1 Mar 2022 10:52]
Erlend Dahl
Duplicate of Bug#98131 Files left after DROP TABLE since InnoDB skips post_ddl for bootstrapping THDs which was fixed in 8.0.20.