<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Innodb on Tony老师的博客</title><link>https://blog.tanteng.space/tags/innodb/</link><description>Recent content in Innodb on Tony老师的博客</description><generator>Hugo</generator><language>zh</language><lastBuildDate>Sat, 22 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.tanteng.space/tags/innodb/index.xml" rel="self" type="application/rss+xml"/><item><title>MySQL 死锁：根源剖析与线上治理实战</title><link>https://blog.tanteng.space/posts/mysql-deadlock-deep-dive/</link><pubDate>Sat, 22 Apr 2023 00:00:00 +0000</pubDate><guid>https://blog.tanteng.space/posts/mysql-deadlock-deep-dive/</guid><description>&lt;p&gt;在分布式高并发的后端架构中，数据库死锁（Deadlock）就像一个幽灵。尽管 InnoDB 引擎具备全自动的自救回滚机制，但频繁出现的死锁报错（错误码 1213）不仅会吞噬系统吞吐量，更是代码健壮性不足的显性信号。本文去掉生活化的类比，直接从&lt;strong&gt;资源竞争的结构本质&lt;/strong&gt;出发，层层递进地拆解 MySQL 死锁的底层逻辑。&lt;/p&gt;</description></item></channel></rss>