# LWLock: LockManager

> 等待读取或更新“重量级”锁的信息。
---

<div class="event-kicker">PostgreSQL 等待事件档案</div>
<div class="event-identity">
  <span>类别<strong>LWLock</strong></span>
  <span>事件<strong><code>LockManager</code></strong></span>
  <span>版本<strong>PG 13-18</strong></span>
  <span>证据<strong>3 个源码位置</strong></span>
</div>

## 官方描述译文 {#official-description}

等待读取或更新“重量级”锁的信息。

| PG 13 | PG 14 | PG 15 | PG 16 | PG 17 | PG 18 |
| :---: | :---: | :---: | :---: | :---: | :---: |
| ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

## 触发机制 {#mechanism}

重量级锁的账本存放在由 LockHashPartitionLock 分区保护的共享哈希表中。获取、授予、释放或检查大量重量级锁时，即使不存在 SQL 层锁冲突，也可能在分区锁上竞争。

## 正常还是麻烦？ {#normal-vs-trouble}

- <span class="severity-normal">**正常:**</span> 普通关系锁与事务锁流量会带来小规模突发。
- <span class="severity-watch">**需要调查:**</span> 持续占比通常来自锁扇出：超大事务、大量分区、频繁 DDL，或成千上万的排队锁请求。

## 诊断 SQL {#diagnostic-sql}

```sql {title="正在等待 LWLock/LockManager 的会话"}
SELECT pid, backend_type, usename, datname, application_name,
       state, now() - query_start AS query_age,
       now() - xact_start AS xact_age,
       wait_event_type, wait_event,
       pg_blocking_pids(pid) AS blocking_pids,
       left(query, 160) AS query
FROM pg_stat_activity
WHERE wait_event_type = 'LWLock'
  AND wait_event = 'LockManager'
ORDER BY query_age DESC NULLS LAST;
```

```sql {title="当前 LWLock 等待分布"}
SELECT wait_event, count(*) AS waiting_sessions,
       count(*) FILTER (WHERE state = 'active') AS active_waiters,
       max(now() - query_start) AS oldest_query
FROM pg_stat_activity
WHERE wait_event_type = 'LWLock'
GROUP BY wait_event
ORDER BY waiting_sessions DESC, wait_event;
```

```sql {title="这些会话的锁与关系上下文"}
SELECT a.pid, l.locktype, l.mode, l.granted, l.fastpath,
       d.datname, n.nspname, c.relname,
       l.page, l.tuple, l.virtualxid, l.transactionid,
       l.classid, l.objid, l.objsubid
FROM pg_stat_activity AS a
LEFT JOIN pg_locks AS l ON l.pid = a.pid
LEFT JOIN pg_database AS d ON d.oid = l.database
LEFT JOIN pg_class AS c
  ON c.oid = l.relation
 AND l.database = (
       SELECT oid FROM pg_database WHERE datname = current_database()
     )
LEFT JOIN pg_namespace AS n ON n.oid = c.relnamespace
WHERE a.wait_event_type = 'LWLock'
  AND a.wait_event = 'LockManager'
ORDER BY a.pid, l.granted, l.locktype, l.mode;
```

## 处置建议 {#response}

1. 按 PID 统计 pg_locks 行数并检查阻塞树。
2. 定位一次触碰大量关系或分区的语句。
3. 缩短事务并降低锁扇出；只有真实容量报错时才提高 max_locks_per_transaction。

## 源码证据 {#source}

- [PostgreSQL 18.6 · src/backend/storage/ipc/ipci.c:117](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/storage/ipc/ipci.c#L117) — `LockManager`
- [PostgreSQL 18.6 · src/backend/storage/lmgr/lwlock.c:739](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/storage/lmgr/lwlock.c#L739) — `pgstat_report_wait_start`
- [PostgreSQL 18.6 · src/backend/utils/activity/wait_event_names.txt:378](https://github.com/postgres/postgres/blob/REL_18_6/src/backend/utils/activity/wait_event_names.txt#L378) — `LockManager`

## 关联控制项与信号 {#related}

- **GUC:** [[guc:max_locks_per_transaction]](/zh/guc/max-locks-per-transaction/) · [[guc:max_connections]](/zh/guc/max-connections/)
- **指标:** [[metric:waiting_sessions]](/zh/metric/waiting-sessions/) · [[metric:wait_event_share]](/zh/metric/wait-event-share/) · [[metric:locks_per_backend]](/zh/metric/locks-per-backend/) · [[metric:blocked_sessions]](/zh/metric/blocked-sessions/)

## 典型事故模式 {#incident}

发布过程对数千分区执行 DDL，同时业务会话获取关系锁；在明显阻塞者出现前，内部锁表已经发生竞争。

---

反链：

- [LWLock](/zh/lwlock/)