[MDEV-20448] Add link to release notes about "Row size too large" errors Created: 2019-08-29  Updated: 2020-05-16  Resolved: 2019-08-30

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Create Table, Documentation, Storage Engine - InnoDB
Fix Version/s: 10.2.26, 10.3.17, 10.4.7

Type: Task Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Daniel Bartholomew
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-19292 "Row size too large" error when creat... Closed
Relates
relates to MDEV-20256 "Row size too large" on latest releas... Closed
relates to MDEV-20268 create table fails with row size too ... Closed
relates to MDEV-20346 Cannot create a certain table: Row si... Closed
relates to MDEV-20400 Implement a way to query an InnoDB ta... Confirmed
relates to MDEV-22585 Incorrect note being written to the e... Open
relates to MDEV-23521 Implement an InnoDB row format that c... Open

 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:

https://mariadb.com/kb/en/library/innodb-row-formats-overview/#upgrading-causes-row-size-too-large-errors

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/



 Comments   
Comment by Daniel Bartholomew [ 2019-08-30 ]

Added note to all of the affected release notes, with a link to the relevant part of the docs as mentioned in the description.

Generated at Thu Feb 08 08:59:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.