Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
The fix for MDEV-19292 has some pretty confusing side effects for some users. I think the release notes for the MariaDB 10.2.26, MariaDB 10.3.17, and MariaDB 10.4.7 releases should mention that this bug is fixed in these versions. I think they should also mention that the change can have some side effects. I think they should also link to the following documentation section to describe the available workarounds:
The release notes do not currently have any details about the bug fix. They just mention that it is related to CREATE TABLE. See here:
https://mariadb.com/kb/en/library/mariadb-10226-release-notes/
https://mariadb.com/kb/en/library/mariadb-10317-release-notes/
https://mariadb.com/kb/en/library/mariadb-1047-release-notes/
Attachments
Issue Links
- is caused by
-
MDEV-19292 "Row size too large" error when creating table with lots columns when row format is DYNAMIC or COMPRESSED
- Closed
- relates to
-
MDEV-20256 "Row size too large" on latest release (10.3.17)
- Closed
-
MDEV-20268 create table fails with row size too large in 10.3 but not 10.1
- Closed
-
MDEV-20346 Cannot create a certain table: Row size too large
- Closed
-
MDEV-20400 Implement a way to query an InnoDB table's max row size
- Open
-
MDEV-22585 Incorrect note being written to the error log when CREATE and ALTER fail due to Row Size Too Large and in all cases for TRUNCATE and OPTIMIZE TABLE.
- Open
-
MDEV-23521 Implement an InnoDB row format that can use overflow pages for smaller columns
- Open