Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2, 10.3.0, 10.4.0, 10.5.0
Description
MySQL 5.7.30 included the following bug fix:
Bug#30437378 : ASSERTION N_EXT == DTUPLE->GET_N_EXT() AT REC_GET_CONVERTED_SIZE() IN REM0REC.IC
It appears to be a follow-up to the MySQL 5.7.29 bug fix which we reported as MDEV-21511:
Bug#30342846 : N_EXT CALCULATION IS NOT CORRECT WHICH CAUSES WRONG RECORD SIZE CALCULATION
This refines an earlier fix in MySQL 5.7.5. I verified that the changed code is covered by the test innodb.blob-crash.
No test case was included for either the MySQL 5.7.29 or 5.7.30 code changes.
Only a part of the change applies to MariaDB. MDEV-11487 removed the function row_update_for_mysql_using_cursor(), which was unused in MariaDB Server.
Attachments
Issue Links
- blocks
-
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Link |
This issue blocks |
| Fix Version/s | 10.2.32 [ 24221 ] | |
| Fix Version/s | 10.3.23 [ 24222 ] | |
| Fix Version/s | 10.4.13 [ 24223 ] | |
| Fix Version/s | 10.5.3 [ 24263 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.3 [ 22126 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 107850 ] | MariaDB v4 [ 157676 ] |