LWLock/WALBufMapping

各版本描述

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

1. 9.6

   LWLockNamed/WALBufMappingLock曾用名

   等待在WAL缓冲区中替换一个页面。

   Waiting to replace a page in WAL buffers.

2. 10–12

   LWLock/WALBufMappingLock曾用名

   等待在WAL缓冲区中替换一个页面。

   Waiting to replace a page in WAL buffers.

3. 13–20

   LWLock/WALBufMapping

   等待在WAL缓冲区中替换一个页面。

   Waiting to replace a page in WAL buffers.

触发机制

WALBufMappingLock 协调 WAL 页号与有限 wal_buffers 槽位之间的映射。后端推进到新 WAL 页或替换缓冲页时需要取得此锁。

WALBufMappingLock coordinates the mapping between WAL page numbers and the finite wal_buffers slots. A backend needs it when advancing to or replacing a WAL buffer page.

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

处置步骤

1. 关联 WAL 字节量、WAL 写入与检查点时间。
2. 检查写突发期间 wal_buffers 是否反复耗尽。
3. 先平滑写突发并解决 WAL 设备延迟，再调整缓冲区大小。

相关参数与指标

wal_bufferscheckpoint_timeoutmax_wal_size waiting_sessionswait_event_sharewal_byteswal_write_time

源码证据

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

演化历史

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

1. PostgreSQL 13 ← 12 更名

   更名 WALBufMappingLock→WALBufMapping

   等待在WAL缓冲区中替换一个页面。

2. PostgreSQL 10 ← 9.6 类型变动

   类型 LWLockNamed→LWLock

   等待在WAL缓冲区中替换一个页面。

3. PostgreSQL 9.6 新增此事件

   9.6 引入等待事件机制，此为本事件的首个版本

   等待在WAL缓冲区中替换一个页面。

同类事件