LWLock/LogicalRepWorker

各版本描述

相邻版本里类型、名称与英文描述都相同的合并成一段，旧的在前。中文取自图谱或本站手册译文，没有译文的只给英文原文。

1. 10–12

   LWLock/LogicalRepWorkerLock曾用名

   等待对逻辑复制工作进程的操作完成。

   Waiting for action on logical replication worker to finish.

2. 13–20

   LWLock/LogicalRepWorker

   等待读取或更新逻辑复制工作进程的状态。

   Waiting to read or update the state of logical replication workers.

触发机制

pgstat_report_wait_start 位于 src/backend/storage/lmgr/lwlock.c:739，是经 grep 核验的报告路径。公共身份/资源映射位于 src/backend/replication/logical/launcher.c:189。探针覆盖的操作是：等待读取或更新逻辑复制 worker 的状态。LWLockAcquire 无法立即取得显示为 LogicalRepWorker 的轻量级锁 tranche；后端在内部共享内存资源上休眠时，通用 LWLock 报告器发布该 tranche 名称。

pgstat_report_wait_start at src/backend/storage/lmgr/lwlock.c:739 is the grep-verified reporting path. The public identity/resource is mapped at src/backend/replication/logical/launcher.c:189. The instrumented operation is: Waiting to read or update the state of logical replication workers. LWLockAcquire could not immediately take the lightweight-lock tranche displayed as LogicalRepWorker. The generic LWLock reporter publishes the tranche name while the backend sleeps on the internal shared-memory resource.

诊断 SQL

直接在 psql 里跑；标注的是语句里用到的视图与列所要求的最低版本。

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 = 'LogicalRepWorker'
ORDER BY query_age DESC NULLS LAST;

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;

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 = 'LogicalRepWorker'
ORDER BY a.pid, l.granted, l.locktype, l.mode;

处置步骤

1. 重复采样并锁定一个热点 tranche。
2. 把它与受保护资源及当前负载阶段关联。
3. 降低具体竞争源；增加并发可能让共享内存热点更糟。

相关参数与指标

waiting_sessionswait_event_share

源码证据

图谱在各版本源码树里核对到的位置，新的在前。「触发点」是真正上报等待事件的调用处，「目录定义」只说明这个名字在枚举里存在。

演化历史

相邻两个大版本之间的差异，新的在前。版本号链到该版的变动清单。

1. PostgreSQL 13 ← 12 更名

   更名 LogicalRepWorkerLock→LogicalRepWorker 描述措辞更新

   等待读取或更新逻辑复制工作进程的状态。

   描述前后对照

   Waiting for action on logical replication worker to finish. Waiting to read or update the state of logical replication workers.

2. PostgreSQL 10 ← 9.6 新增此事件

   该版起出现

   等待对逻辑复制工作进程的操作完成。

同类事件