Bug #80182 | Unsupported extension error for new features while 'create table like' | ||
---|---|---|---|
Submitted: | 28 Jan 2016 7:31 | Modified: | 16 Mar 2016 15:36 |
Reporter: | Shahriyar Rzayev | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | 5.7.10 | OS: | CentOS (7) |
Assigned to: | CPU Architecture: | Any |
[28 Jan 2016 7:31]
Shahriyar Rzayev
[28 Jan 2016 9:18]
MySQL Verification Team
Hello Shahriyar, Thank you for the report. Verified as described with 5.7.10. Thanks, Umesh
[5 Feb 2016 6:48]
Kevin Lewis
Posted by developer: This bug is really a problem with allowing a table to be assign compression='lz4' when that table is in a shared general tablespace. Transparent Page Compression was intended to only work with File-Per_table Tablespaces. The metadata and the SQL used to assign page compression is on a single table, but it is applied to all pages of the tablespace. So Things get confused when there can be multiple tables in a tablespace.
[16 Mar 2016 15:36]
Daniel Price
Posted by developer: Fixed as of the upcoming 5.7.13, 5.8.0 release, and here's the changelog entry: Validation code for transparent page compression incorrectly permitted innodb_strict_mode=OFF, which allowed the COMPRESSION attribute to be applied to a general tablespace. Page compression is only supported with file-per-table tablespaces. Thank you for the bug report.
[31 Mar 2016 5:15]
Erlend Dahl
Bug#80389 Irrelevant warning while altering tablespace of compression='none' table was marked as a duplicate.