| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: bufmgr: Avoid spurious compiler warning after fcb9c977aa5 |
| Date: | 2026-01-16 12:02:29 |
| Message-ID: | E1vgiX7-000nIC-0X@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(at)sss(dot)pgh(dot)pa(dot)us>
Discussion: https://postgr.es/m/934395.1768518154@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/84705b37273da016633fc5c0a06e848bd6e1e71b
Modified Files
--------------
src/backend/storage/buffer/bufmgr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2026-01-16 12:40:26 | pgsql: Fix rare test failure in nbtree_half_dead_pages |
| Previous Message | Michael Paquier | 2026-01-16 06:25:37 | pgsql: Improve pg_clear_extended_stats() with incorrect relation/stats |