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 <[email protected]> Discussion: https://postgr.es/m/[email protected] 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(-)
