replace into 产生死锁

当执行replace into语句时，如果旧行和新行（要插入的数据）的主键或唯一键发生冲突，replace into语句会相当于先执行delete语句删除旧行，然后再执行insert语句插入新数据。在生产环境中，当多个事务同时执行replace into语句，并且它们同时尝试获取锁时，可能会导致死锁的发生。当事务1和事务2同时执行replace into语句，并且它们尝试获取的锁存在冲突时，事务1会被事务2阻塞，同时事务2也会被事务1阻塞，从而导致死锁并触发回滚操作。为了避免死锁的发生，可以考虑调整事务的并发控制策略，例如通过调整事务的隔离级别、合理设计数据库索引、调整事务的执行顺序等方式来减少死锁的概率。<span class="em">1</span><span class="em">2</span><span class="em">3</span>
#### 引用[.reference_title]
- *1* [记一次replace into引发的死锁问题](https://blog.csdn.net/weiweiracings/article/details/121018687)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT3_1"}}] [.reference_item style="max-width: 33.333333333333336%"]
- *2* [高并发状态下Replace Into造成的死锁问题思考](https://blog.csdn.net/m0_56289903/article/details/121007012)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT3_1"}}] [.reference_item style="max-width: 33.333333333333336%"]
- *3* [replace into 引发的死锁问题](https://blog.csdn.net/weixin_32391045/article/details/113593693)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v92^chatsearchT3_1"}}] [.reference_item style="max-width: 33.333333333333336%"]
[ .reference_list ]