Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.27, 10.3.18, 10.4.8
-
None
Description
If a user executes DDL that effects a table which has too large rows, then the error log will contain a message like the following:
2019-07-28 0:57:51 140189814937344 [Warning] InnoDB: Cannot add field `c08` in table `test`.`t1` because after adding it, the row size is 2484 which is greater than maximum allowed size (1982) for a record on index leaf page.
|
(I believe the specific message may change in the patch for MDEV-20194.)
With the default value of innodb_strict_mode=ON, it will be an error. If the user sets innodb_strict_mode=OFF, then it will be a warning.
https://mariadb.com/kb/en/library/troubleshooting-row-size-too-large-errors-with-innodb/
Some users think that it should be possible to suppress this warning in the error log if the user sets innodb_strict_mode=OFF.
By default, log_warnings is set to 2.
https://mariadb.com/kb/en/library/server-system-variables/#log_warnings
Maybe this warning should only be printed when innodb_strict_mode=OFF if log_warnings > 2, so that it doesn't get printed to the error log by default.
Attachments
Issue Links
- relates to
-
MDEV-21261 When performing instant add column, InnoDB ignores innodb_strict_mode for "row size too large" check
-
- Confirmed
-
-
MDEV-16969 Fix error message as promised in upstream Bug #69336
-
- Open
-
-
MDEV-19292 "Row size too large" error when creating table with lots columns when row format is DYNAMIC or COMPRESSED
-
- Closed
-
-
MDEV-20194 Warnings inconsistently issued upon CHECK on table from older versions
-
- Closed
-
-
MDEV-20400 Implement a way to query an InnoDB table max row size
-
- Open
-
-
MDEV-20786 MariaDB server writes warnings into errorlog although 'log_warnings=0'
-
- Closed
-
-
MDEV-20949 Stop performing unnecessary maximum row size check for DML
-
- Closed
-
-
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
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Link |
This issue relates to |
Link | This issue relates to MDEV-20400 [ MDEV-20400 ] |
Link | This issue relates to MDEV-16969 [ MDEV-16969 ] |
Link |
This issue relates to |
Summary | Don't print "row size too large" warnings in error log if innodb_strict_mode=OFF and log_warnings=2 | Don't print "row size too large" warnings in error log if innodb_strict_mode=OFF and log_warnings<=2 |
Link |
This issue relates to |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Eugene Kosov [ kevg ] | Thirunarayanan Balathandayuthapani [ thiru ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Link | This issue relates to MENT-514 [ MENT-514 ] |
issue.field.resolutiondate | 2019-11-20 13:09:51.0 | 2019-11-20 13:09:51.58 |
Fix Version/s | 10.2.30 [ 24015 ] | |
Fix Version/s | 10.3.21 [ 24014 ] | |
Fix Version/s | 10.4.11 [ 24013 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Assignee | Thirunarayanan Balathandayuthapani [ thiru ] | Eugene Kosov [ kevg ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10002 ] | Closed [ 6 ] |
Link | This issue relates to MDEV-21261 [ MDEV-21261 ] |
Link | This issue relates to MDEV-22585 [ MDEV-22585 ] |
Workflow | MariaDB v3 [ 100421 ] | MariaDB v4 [ 156865 ] |
Zendesk Related Tickets | 147879 113644 118409 185863 160501 150204 114072 195104 198426 164062 166795 159353 |