排查postgresql 15中join操作的死锁,核心在于识别持有互斥锁的查询并终止其中一方。具体做法是查询系统视图 pg_locks 和 pg_stat_activity,找出处于 waiting 状态且持有 rowexclusivelock 或 accesssharelock 的事务,然后使用 pg_terminate_backend() 函数强制结束阻塞源。这样做能立即解除死锁僵局,恢复数据库正常运行。

如何定位导致死锁的具体SQL语句
定位导致死锁的SQL语句需要结合事务ID和进程ID进行关联查询。通过检查 pg_locks 视图中等待锁的记录,可以获取阻塞者的 pid,进而从 pg_stat_activity 中提取完整的 query 文本。这种方法能精准锁定引发冲突的JOIN操作代码。

-- 查找当前正在等待锁的进程及其阻塞者
SELECT
blocked_locks.pid AS blocked_pid,
blocked_activity.query AS blocked_query,
blocking_locks.pid AS blocking_pid,
blocking_activity.query AS blocking_query
FROM pg_catalog.pg_locks blocked_locks
JOIN pg_catalog.pg_stat_activity blocked_activity ON blocked_locks.pid = blocked_activity.pid
JOIN pg_catalog.pg_locks blocking_locks
ON blocked_locks.locktype = blocking_locks.locktype
AND blocked_locks.database IS NOT DISTINCT FROM blocking_locks.database
AND blocked_locks.relation IS NOT DISTINCT FROM blocking_locks.relation
AND blocked_locks.page IS NOT DISTINCT FROM blocking_locks.page
AND blocked_locks.tuple IS NOT DISTINCT FROM blocking_locks.tuple
AND blocked_locks.virtualxid IS NOT DISTINCT FROM blocking_locks.virtualxid
AND blocked_locks.transactionid IS NOT DISTINCT FROM blocking_locks.transactionid
AND blocked_locks.classid IS NOT DISTINCT FROM blocking_locks.classid
AND blocked_locks.objid IS NOT DISTINCT FROM blocking_locks.objid
AND blocked_locks.objsubid IS NOT DISTINCT FROM blocking_locks.objsubid
AND blocked_locks.pid != blocking_locks.pid
JOIN pg_catalog.pg_stat_activity blocking_activity ON blocking_locks.pid = blocking_activity.pid
WHERE NOT blocked_locks.granted;
预期结果:返回两行关键信息,blocked_query 显示正在执行JOIN且被挂起的SQL,blocking_query 显示持有锁但尚未提交的SQL。若两者均为复杂的JOIN语句,则确认死锁由并发JOIN引起。
如何安全地终止阻塞进程以解除死锁
安全终止阻塞进程需使用 pg_terminate_backend(pid) 函数,该函数会发送SIGTERM信号给指定进程,使其优雅退出并释放所有锁。在执行前必须确认 pid 属于非关键业务进程,避免误杀主连接。此操作能迅速打破死锁循环,无需重启数据库。

-- 假设上一步查询得到的阻塞者PID为 12345 SELECT pg_terminate_backend(12345);
预期结果:函数返回布尔值 true,表示信号发送成功。随后 pg_stat_activity 中该 pid 的状态变为 idle 或记录消失,死锁解除。被终止的进程会收到错误 terminating connection due to administrator command,其未提交的事务回滚,锁释放。
当JOIN涉及大表时如何预防此类死锁
当JOIN涉及大表时,预防死锁的关键是确保所有事务以相同顺序访问表,并缩短事务持有锁的时间。具体做法是在应用层对JOIN涉及的表进行排序后依次加锁,或使用 SET lock_timeout 设置超时自动重试。此外,将大表JOIN拆分为小批次处理可减少锁竞争范围。










