[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. Created: 2020-05-15 Updated: 2023-04-27 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Data Definition - Create Table, Storage Engine - InnoDB |
| Affects Version/s: | 10.2.31, 10.3.22, 10.4.12, 10.5.2 |
| Fix Version/s: | 10.4, 10.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Juan | Assignee: | Thirunarayanan Balathandayuthapani |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | logging | ||
| Environment: |
CentOS 7 |
||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
When innodb_strict_mode is on, table creation and every alter table that would result in a too-large row size fails, issuing an error 1118:
and logs a different but technically correct message to the error log:
However, when innodb_strict_mode=0 the error message becomes a warning message:
but the same message written to the error log as an error when innodb_strict_mode was set to 1 gets written to the error log as a warning:
The same problem happens with TRUNCATE TABLE and OPTIMIZE TABLE operations. However, these operations succeed and write the incorrect message to the log regardless of the value of innodb_strict_mode. which is incorrect. The table gets successfully created with all fields including c181 and c182-c200. |