[MDEV-22384] Wrong estimate of affected BLOB columns in update of PRIMARY KEY Created: 2020-04-28  Updated: 2020-05-04  Resolved: 2020-05-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2.2, 10.3.0, 10.4.0, 10.5.0
Fix Version/s: 10.2.32, 10.3.23, 10.4.13, 10.5.3

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: blob

Issue Links:
Blocks
blocks MDEV-22394 Merge new release of InnoDB 5.7.30 to... Closed
Relates
relates to MDEV-21511 Wrong estimate of affected BLOB colum... Closed

 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.
Generated at Thu Feb 08 09:14:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.