[MDEV-31165] Feature Request - Add innodb data_locks and data_lock_waits, or better, tables Created: 2022-03-09  Updated: 2023-12-05

Status: Open
Project: MariaDB Server
Component/s: Performance Schema
Fix Version/s: None

Type: Task Priority: Major
Reporter: Anders Karlsson Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: Migration


 Description   

The data_locks and data_lock_waits performance_schema tables, available in MySQL 8.0, is a bit different from the information_schema innodb_locks and innodb_lock_waits. The main difference is that the performance_schema tables show locks even when nothing is waiting for them. It would be even better to be able to identify individual row locks.
The usefulness of this type of monitoring is when having complex transactions which might interlock and cause deadlocks. This is often an issue when migrating from other database systems where locking is different than in MariaDB.



 Comments   
Comment by Vladislav Lesin [ 2023-12-05 ]

The initial commit in MySQL is:

commit 2bb0216eec4386d6d3338a5f6784005044711118
Author: Marc Alff <marc.alff@oracle.com>
Date:   Tue Sep 13 16:04:54 2016 +0200
 
    WL#6657 PERFORMANCE_SCHEMA LOCK_DATA

https://dev.mysql.com/worklog/task/?id=6657

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