Hi,

The four backend-specific paths in WaitEventSetWaitBlock()
(epoll, kqueue, poll, and Windows) had identical-purpose comments
with inconsistent spellings.

Two comments used "writable" while the other two used "writeable".

This patch standardizes the spelling to "writable" to match the
surrounding text in the file.

The WL_SOCKET_WRITEABLE macro is a public identifier and is left
unchanged.

Patch attached.
From 2a8210a49cb3cb3771c6ff6711385f366ec861ee Mon Sep 17 00:00:00 2001
From: cybrosys <[email protected]>
Date: Wed, 6 May 2026 15:11:40 +0530
Subject: [PATCH] Make spelling consistent in waiteventset.c

The four backend-specific paths in WaitEventSetWaitBlock() (epoll,
kqueue, poll, and Windows) had identical-purpose comments that used
inconsistent spellings: two said "writable, or EOF" while the other
two said "writeable". Standardize on "writable" to match the spelling
already used in the surrounding running text of the file. The
WL_SOCKET_WRITEABLE macro is a public identifier and is left
unchanged.

Co-Authored-By: [email protected]
---
 src/backend/storage/ipc/waiteventset.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/storage/ipc/waiteventset.c b/src/backend/storage/ipc/waiteventset.c
index 627dba0a842..f3cfbbccd1e 100644
--- a/src/backend/storage/ipc/waiteventset.c
+++ b/src/backend/storage/ipc/waiteventset.c
@@ -1570,7 +1570,7 @@ WaitEventSetWaitBlock(WaitEventSet *set, int cur_timeout,
 			if ((cur_event->events & WL_SOCKET_WRITEABLE) &&
 				(cur_pollfd->revents & (POLLOUT | errflags)))
 			{
-				/* writeable, or EOF */
+				/* writable, or EOF */
 				occurred_events->events |= WL_SOCKET_WRITEABLE;
 			}
 
@@ -1800,7 +1800,7 @@ WaitEventSetWaitBlock(WaitEventSet *set, int cur_timeout,
 			if ((cur_event->events & WL_SOCKET_WRITEABLE) &&
 				(resEvents.lNetworkEvents & FD_WRITE))
 			{
-				/* writeable */
+				/* writable */
 				occurred_events->events |= WL_SOCKET_WRITEABLE;
 			}
 			if ((cur_event->events & WL_SOCKET_CONNECTED) &&
-- 
2.34.1

Reply via email to