Frequent data operations will cause It is possible to access the aggregate index and the non-aggregate index successively, thus blocking each other and forming a deadlock. The deadlock may be locked on different resources, or it may be locked on the same resource. It can Understand the principle of deadlock and the principle of execution engine locking. Generally, operating resources in the same order, not using a higher level transaction isolation level or using optimistic locking is the solution. How to do it depends on how you write your query and how you build the index.
The cause of deadlock is resource competition. Waiting for each other leads to deadlock.
The attack is not just a deadlock problem. Check the cause from the program.
It should just be a deadlock problem. The reason is: an increase in concurrent operations, an increase in the number of users, and functional defects. For example, the same resources, such as the same data in the same table, will be used by multiple users at the same time, and the functional design is repeated. Internal processing has its own sequence.
It is recommended to ask a DBA to help you take a look.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Frequent data operations will cause
It is possible to access the aggregate index and the non-aggregate index successively, thus blocking each other and forming a deadlock.
The deadlock may be locked on different resources, or it may be locked on the same resource. It can Understand the principle of deadlock and the principle of execution engine locking.
Generally, operating resources in the same order, not using a higher level transaction isolation level or using optimistic locking is the solution. How to do it depends on how you write your query and how you build the index.
The cause of deadlock is resource competition. Waiting for each other leads to deadlock.
The attack is not just a deadlock problem. Check the cause from the program.
It should just be a deadlock problem. The reason is: an increase in concurrent operations, an increase in the number of users, and functional defects. For example, the same resources, such as the same data in the same table, will be used by multiple users at the same time, and the functional design is repeated. Internal processing has its own sequence.
It is recommended to ask a DBA to help you take a look.