[MDEV-28443] MDEV-15250 causes latch order violation Created: 2022-04-29  Updated: 2022-05-03  Resolved: 2022-04-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: N/A
Fix Version/s: 10.6.8, 10.7.4, 10.8.3, 10.9.1

Type: Bug Priority: Blocker
Reporter: Thirunarayanan Balathandayuthapani Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: regression

Issue Links:
Problem/Incident
is caused by MDEV-15250 UPSERT during ALTER-TABLE results in ... Closed
Relates
relates to MDEV-27983 InnoDB hangs on multiple concurrent r... Closed

 Description   

MDEV-15250 introduced latch order violation that index page latches must be acquired before undo log pages latches. But in trx_t::apply_log(), we do acquire undo log page latch before taking index page latch.

InnoDB should copy the undo log record in trx_t::apply_log() and release the
undo log block

 Comments   
Comment by Thirunarayanan Balathandayuthapani [ 2022-04-29 ]

MDEV-15250 introduced latch order violation that index page latches must be acquired before undo log pages latches. But in trx_t::apply_log(), we do acquire undo log page latch before taking index page latch.

InnoDB should copy the undo log record in trx_t::apply_log() and release the
undo log block

Comment by Thirunarayanan Balathandayuthapani [ 2022-04-29 ]

Patch is in bb-10.6-MDEV-28443

Generated at Thu Feb 08 10:00:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.