跳转到主要内容

IO: LogicalSubxactRead

等待从逻辑子事务文件中读取数据。
PostgreSQL 等待事件档案
类别IO 事件LogicalSubxactRead 版本PG 14 证据1 个源码位置

官方描述译文

等待从逻辑子事务文件中读取数据。

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

触发机制

目录中仍保留该身份,但源码审计确认在 14 已没有活动报告点。已知曾可触发范围:none。下方定义位置作为负面证据保留;当前精确版本不会从核心代码路径发出此事件。 证据:pgsql-hackers confirmation

正常还是麻烦?

  • 正常: 在已审计的精确版本上,不应出现活动的核心触发。
  • 需要调查: 若监控仍显示它,应核对精确小版本、扩展来源,并确认样本是否陈旧或来自另一台服务器。

诊断 SQL

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

处置建议

  1. 确认当前负载阶段本来就应访问这类文件。
  2. 在可用版本上关联 pg_stat_io 与具体设备延迟。
  3. 先修复访问路径、突发形状或受影响存储层,再调整无关的内存参数。

源码证据