Hi, Aleksey, On Sep 11, Aleksey Midenkov wrote:
revision-id: 75ea482c4fc (mariadb-11.0.1-230-g75ea482c4fc) parent(s): fe62f70fb4b author: Aleksey Midenkov committer: Aleksey Midenkov timestamp: 2023-09-01 20:30:24 +0300 message:
MDEV-30973 GTID in deadlock output
Example:
TRANSACTION 40, ACTIVE 0 sec starting index read mysql tables in use 1, locked 1 LOCK WAIT 2 lock struct(s), heap size 1152, 1 row lock(s) MySQL thread id 23, OS thread handle 140201491547840, query id 310, GTID 3-1-1 Updating delete from tu where a = 9999 and b = 'xxxx' 2023-04-12 19:53:58 22 [Note] InnoDB: *** (1) WAITING FOR THIS LOCK TO BE GRANTED:
Deterministic slave_deadlock.test
Instead of "MDEV-10962 Deadlock with 3 concurrent DELETEs by unique key" this one uses "MDEV-22698 Deadlock on concurrent acquisition from multiple indexes"
--- mysql-test/suite/rpl/t/slave_deadlock.test | 93 ++++++++++++++++++++++++++++++ sql/sql_show.cc | 10 ++++
please move slave_deadlock.result from the following commit to this one. otherwise ok Regards, Sergei VP of MariaDB Server Engineering and security@mariadb.org