Bug #93524 can/cannot move table from ibdata1 to ibd.
Submitted: 8 Dec 2018 1:13 Modified: 13 Dec 2018 15:31
Reporter: Rick James Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.6, 5.7, 8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: ALTER TABLE, ibd, innodb_file_per_table, Tablespace

[8 Dec 2018 1:13] Rick James
"innodb_file_per_table is enabled by default, which prevents ALTER TABLE from moving InnoDB tables from the system tablespace to individual .ibd files."

This seems wrong, or at least confusing.

-- https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_file_per_tabl...

Also 5.6, 5.7

How to repeat:
See docs

Suggested fix:
Remove that paragraph.
[8 Dec 2018 7:00] MySQL Verification Team
Hello Rick,

Thank you for the bug report and feedback.

[13 Dec 2018 15:31] Daniel Price
Posted by developer:
The referenced content has been revised as follows:

"When innodb_file_per_table is enabled, a table-copying ALTER TABLE operation on a table that resides in the system tablespace implicitly re-creates the table in a file-per-table tablespace. To prevent this from occurring, disable innodb_file_per_table before executing table-copying ALTER TABLE operations on tables that reside in the system tablespace."

This behavior no longer occurs in MySQL 8.0.

Thank you for the bug report.