pgsql: Move WAIT_FOR_WAL_* wait events from Client to IPC class

From: Alexander Korotkov <akorotkov(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Move WAIT_FOR_WAL_* wait events from Client to IPC class
Date: 2026-07-08 18:00:01
Message-ID: E1whWYy-000AzI-2h@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Move WAIT_FOR_WAL_* wait events from Client to IPC class

WAIT_FOR_WAL_FLUSH, WAIT_FOR_WAL_REPLAY, and WAIT_FOR_WAL_WRITE were
placed in the WaitEventClient class. But WaitEventClient is about
waiting for a socket to become readable or writable, while these events
have other delay sources as well: local fsync and local replay, which
may be disk- or CPU-bound. WaitEventIPC is a better fit, so move them
there.

Reported-by: Noah Misch <noah(at)leadboat(dot)com>
Discussion: https://postgr.es/m/20260706012642.f9.noahmisch@microsoft.com
Backpatch-through: 19

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/306d7680f084cf320841128f23d888294ecba6cd

Modified Files
--------------
src/backend/utils/activity/wait_event_names.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2026-07-08 19:49:20 pgsql: Fix RETURNING OLD with BEFORE UPDATE trigger and concurrent upda
Previous Message Alexander Korotkov 2026-07-08 18:00:00 pgsql: Move WAIT_FOR_WAL_* wait events from Client to IPC class