Bug #110383 | After ALTER, TABLESPACE is incorrectly explicit with innodb_file_per_table=0 | ||
---|---|---|---|
Submitted: | 15 Mar 2023 21:04 | Modified: | 16 Mar 2023 6:16 |
Reporter: | Jeremy Cole (Basic Quality Contributor) (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Data Dictionary | Severity: | S3 (Non-critical) |
Version: | 8.0.32 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | alter, data dictionary, Tablespace |
[15 Mar 2023 21:04]
Jeremy Cole
[16 Mar 2023 13:12]
MySQL Verification Team
Hi Jeremy, Thank you for your contribution .......
[14 Aug 10:32]
Pavel Yurin
When moving from innodb_file_per_table=0 to a MySQL instance with innodb_file_per_table enabled, some tables may still be created in ibdata1 instead of separate .ibd files.