Bug #93499 | Innodb tablespaces with subpartitions do not contain Table SDI object | ||
---|---|---|---|
Submitted: | 6 Dec 2018 5:46 | Modified: | 23 Mar 2019 13:40 |
Reporter: | Sergei Glushchenko | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Data Dictionary | Severity: | S3 (Non-critical) |
Version: | 8.0.13 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[6 Dec 2018 5:46]
Sergei Glushchenko
[6 Dec 2018 6:03]
MySQL Verification Team
Hello Sergei, Thank you for the report and test case. Thanks, Umesh
[1 Mar 2019 14:40]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.17 release, and here's the changelog entry: Serialized Dictionary Information (SDI) was not stored in any tablespace file for tables with subpartitions. SDI data should be stored in the tablespace file of the first partition.
[5 Mar 2019 11:55]
Daniel Price
Posted by developer: commit 53252d9f1556425e89c8275220cf48215a26f804 Author: Mauritz Sundell <mauritz.sundell@oracle.com> Date: Fri Mar 1 16:21:51 2019 +0100 Revert "Bug#29020745: INNODB TABLESPACES WITH SUBPARTITIONS DO NOT CONTAIN TABLE SDI" This reverts commit 1b2d32392cfaf69cec2835e8693fd748a61fd19d. Approved-by: Kari Wedde <kari.wedde@oracle.com>
[5 Mar 2019 11:55]
Daniel Price
Posted by developer: Patch reverted. Changelog entry removed.
[5 Mar 2019 12:29]
Daniel Price
Posted by developer: Changed status back to VERIFIED.
[23 Mar 2019 13:40]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.17 release, and here's the changelog entry: When using subpartitioning, table Serialized Dictionary Information (SDI) was not stored in any of the tablespace files.