Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.4.25, 10.6.8
-
openSUSE Leap 15.3
Description
After dropping/adding some columns multiple times to an InnoDB table the error "ERROR 1118 (42000) at line 405: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs" occurs.
This behaviour is inconsistent, at table creation time there is no error when i then drop some of the columns and add these again within multiple ALTER statements the error suddenly occurs.
If i repeat the drop/add statements often enough with "innodb_strict_mode = Off" the error message disappears after some repetition.
I can reproduce it always with attached sql-file.
The issue doesn't exist within MariaDB-10.3.34 but occurs at least in 10.4.25 and 10.6.8.
This message appears within the error-log: "[ERROR] InnoDB: Cannot add field `c_540` in table `test`.`testme` because after adding it, the row size is 8145 which is greater than maximum allowed size (8126 bytes) for a record on index leaf page."
Attachments
Issue Links
- relates to
-
MDEV-15562 Instant DROP COLUMN or changing the order of columns
- Closed
-
MDEV-20590 Introduce a file format constraint to ALTER TABLE
- Closed