Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4(EOL), 10.5, 10.6, 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
-
None
Description
Error log contains
2023-09-07 23:01:37 4 [ERROR] InnoDB: Cannot add field `f32` in table `mysqld.1`.`#sql-temptable-60cc-4-f` because after adding it, the row size is 8187 which is greater than maximum allowed size (8126 bytes) for a record on index leaf page.
|
instead of
2023-09-07 23:01:37 4 [ERROR] InnoDB: Cannot add field `f32` in table `test`.`t1` because after adding it, the row size is 8187 which is greater than maximum allowed size (8126 bytes) for a record on index leaf page.
|
Attachments
Activity
Partition names don't matter in this context as all partitions have the same table structure. That is when any partition violates the InnoDB restriction the whole table needs to be created differently.
Actually, no. If one can create different partitions using different InnoDB page size, then, indeed, the error might apply only to a specific partition, and then the partition name would be meaningful to know too
InnoDB page size cannot be changed after MariaDB bootstrap. All partitions has the same page size.
Looks good to me. However, if MDEV-22168 is implemented, it would be nice to be able to identify the partition. Partition names are part of the InnoDB table name, but not the SQL layer table name.