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:	None
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

Description:
"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.

Hello Rick,

Thank you for the bug report and feedback.

Thanks,
Umesh

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.

Page generated in 0.050 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.