![]() ![]() *** (1) WAITING FOR THIS LOCK TO BE GRANTED: MySQL thread id 1319, OS thread handle 0x1c64, query id 260771445 localhost 127.0.0.1 root Sending data TRANSACTION 2264758566, ACTIVE 1 sec fetching rows Spin rounds per wait: 1.56 mutex, 5.61 RW-shared, 13.37 RW-excl OS WAIT ARRAY INFO: signal count 182953746 OS WAIT ARRAY INFO: reservation count 21290331 Srv_master_thread log flush and writes: 2188289 Srv_master_thread loops: 2170553 srv_active, 0 srv_shutdown, 17765 srv_idle Per second averages calculated from the last 35 seconds JOIN indicators.fileso fo ON foi.uniqueness = fo.uniqueness P_ParentPath ,ar_regPath, ar_regKey, ar_regValue, hostName, extension, p_parentUser, Transaction A (2 in status): INSERT IGNORE INTO indicators.fileso (hostId, sha256, p_runningUser, NTFSOwner, fullPath,įileName, s_serviceName, d_driverName, p_commandLineParams, So with that logic my conclusion is that an insert ignore (without any select/join or use of another resource) will never create a deadlock.(since it uses only 1 resource), in the worse case a lock wait will be created.īut when I look in the show engine innodb status I can see a deadlock for that kind of transaction. As far as I know and read so many time dead locks only happens when one transaction is locking resource A and waiting for B and another transaction does the opposite. ![]()
0 Comments
Leave a Reply. |