postgres.git / summary / log / commit / refs

commit    84705b37273da016633fc5c0a06e848bd6e1e71b
Author:   Andres Freund <andres@anarazel.de>
Date:     Fri Jan 16 11:58:35 2026 +0000

    bufmgr: Avoid spurious compiler warning after fcb9c977aa5
    
    Some compilers, e.g. gcc with -Og or -O1, warn about the wait_event in
    BufferLockAcquire() possibly being uninitialized. That can't actually happen,
    as the switch() covers all legal lock mode values, but we still need to
    silence the warning.  We could add a default:, but we'd like to get a warning
    if we were to get a new lock mode in the future.  So just initialize
    wait_event to 0.
    
    Reported-by: Tom Lane <tgl@sss.pgh.pa.us>
    Discussion: https://postgr.es/m/934395.1768518154@sss.pgh.pa.us


 src/backend/storage/buffer/bufmgr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/storage/buffer/bufmgr.c b/src/backend/storage/buffer/bufmgr.c
index f30cf93b04f..6f935648ae9 100644
--- a/src/backend/storage/buffer/bufmgr.c
+++ b/src/backend/storage/buffer/bufmgr.c
@@ -5777,8 +5777,8 @@ BufferLockAcquire(Buffer buffer, BufferDesc *buf_hdr, BufferLockMode mode)
 
 	for (;;)
 	{
+		uint32		wait_event = 0; /* initialized to avoid compiler warning */
 		bool		mustwait;
-		uint32		wait_event;
 
 		/*
 		 * Try to grab the lock the first time, we're not in the waitqueue


[parent: 395b73c045e0]