Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.26, 5.5.57, 10.0.32, 10.2.9
Description
A user is seeing an 'Undo log record is too big.' error that only occurs if they update 2 mediumtext fields at once, and if the length of the existing values in each those fields happen to be between 3962 and 4030 characters long.
Some other interesting notes about this:
- The table definition has ROW_FORMAT=COMPACT, so it uses the Antelope format.
- The only indexes on the two mediumtext fields have prefix lengths of 255.
- The problem is repeatable on MySQL 5.5 and 5.7, and MariaDB 10.1 and 10.2, so I don't think it has been fixed in any released version of MySQL or MariaDB.
I have attached an SQL file that can be used to reproduce this issue.
Upstream bug report:
Attachments
Issue Links
- relates to
-
MDEV-11657 Cross-engine transaction metadata
- Open
-
MDEV-14799 After UPDATE of indexed columns, old values will not be purged from secondary indexes
- Closed
-
MDEV-29666 InnoDB fails to purge secondary index records when indexed virtual columns exist
- Closed