跳转到主要内容

Client: LibpqwalreceiverReceive

在 WAL receiver 中等待从远程服务器接收数据。
PostgreSQL 等待事件档案
类别Client 事件LibpqwalreceiverReceive 版本PG 17-18 证据4 个源码位置

官方描述译文

在 WAL receiver 中等待从远程服务器接收数据。

PG 13 PG 14 PG 15 PG 16 PG 17 PG 18

历史名称:Client/LibPQWalReceiverReceive (PG 13-16)

触发机制

WAIT_EVENT_LIBPQWALRECEIVER_RECEIVE 位于 src/backend/replication/libpqwalreceiver/libpqwalreceiver.c:876,是经 grep 核验的报告路径。公共身份/资源映射位于 src/backend/utils/activity/wait_event.c:283。探针覆盖的操作是:在 WAL receiver 中等待从远程服务器接收数据。前端协议路径在套接字、TLS/GSS 或复制客户端操作即将阻塞前报告 LibpqwalreceiverReceive;PostgreSQL 正在等待远端或网络推进。

正常还是麻烦?

  • 正常: 空闲状态的 ClientRead 通常只是连接池存量。
  • 需要调查: 活动写入、握手、很老的 idle in transaction、连接耗尽或复制客户端停滞时需要调查。

诊断 SQL

正在等待 Client/LibpqwalreceiverReceive 的会话
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 = 'Client'
  AND wait_event = 'LibpqwalreceiverReceive'
ORDER BY query_age DESC NULLS LAST;
当前 Client 等待分布
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 = 'Client'
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 = 'Client'
  AND a.wait_event = 'LibpqwalreceiverReceive'
ORDER BY a.pid, l.granted, l.locktype, l.mode;

处置建议

  1. 先看 state 与事务年龄,再决定它是否算负载。
  2. 关联负责的应用、连接池与网络路径。
  3. 修复消费者背压或连接池策略,不要反复终止连接。

源码证据