IO: WalsenderTimelineHistoryRead

Official description

Waiting for a read from a timeline history file during a walsender timeline command

Earlier names: IO/WALSenderTimelineHistoryRead (PG 13-16)

Trigger mechanism

WAIT_EVENT_WALSENDER_TIMELINE_HISTORY_READ at src/backend/replication/walsender.c:654 is the grep-verified reporting path. The public identity/resource is mapped at src/backend/utils/activity/wait_event.c:730. The instrumented operation is: Waiting for a read from a timeline history file during a walsender timeline command. PostgreSQL reports WalsenderTimelineHistoryRead around the instrumented file or asynchronous-I/O operation named by this event. The backend resumes after the kernel, storage stack, or I/O worker completes that step.

Normal or trouble?

• Normal: The wait is normal when the workload is expected to perform this read, write, sync, allocation, or completion operation at the observed rate.
• Investigate: Investigate when it persists with foreground latency, many concurrent waiters, storage tail latency, throttling, or errors.

Diagnostic SQL

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

Response

1. Confirm the workload phase should touch this file class.
2. Correlate with pg_stat_io where available and per-device latency.
3. Fix the access path, burst shape, or affected storage tier before tuning unrelated memory settings.

Source evidence

• PostgreSQL 16.15 · src/backend/replication/walsender.c:654 — WAIT_EVENT_WALSENDER_TIMELINE_HISTORY_READ
• PostgreSQL 16.15 · src/backend/utils/activity/wait_event.c:730 — WALSenderTimelineHistoryRead
• PostgreSQL 18.6 · src/backend/replication/walsender.c:637 — WAIT_EVENT_WALSENDER_TIMELINE_HISTORY_READ
• PostgreSQL 18.6 · src/backend/utils/activity/wait_event_names.txt:263 — WALSENDER_TIMELINE_HISTORY_READ

Related controls and signals

• GUCs: [guc:wal_buffers] · [guc:synchronous_commit]
• Metrics: [metric:waiting_sessions] · [metric:wait_event_share] · [metric:wal_bytes] · [metric:wal_write_time] · [metric:io_read_time] · [metric:io_write_time]