From b177a14a375c53fe95819e1820058dc2bc69e0cf Mon Sep 17 00:00:00 2001 From: Melanie Plageman Date: Mon, 2 Feb 2026 13:27:22 -0500 Subject: [PATCH v14 01/12] Make FlushUnlockedBuffer use its parameters No current callers were passing other values for io_context and io_object, so it is not an active bug. But it is best to make it use the parameters in case future callers do pass other IOContexts or IOObjects. --- 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 d1babaff023..1f26eda9fe4 100644 --- a/src/backend/storage/buffer/bufmgr.c +++ b/src/backend/storage/buffer/bufmgr.c @@ -4557,7 +4557,7 @@ FlushUnlockedBuffer(BufferDesc *buf, SMgrRelation reln, Buffer buffer = BufferDescriptorGetBuffer(buf); BufferLockAcquire(buffer, buf, BUFFER_LOCK_SHARE); - FlushBuffer(buf, reln, IOOBJECT_RELATION, IOCONTEXT_NORMAL); + FlushBuffer(buf, reln, io_object, io_context); BufferLockUnlock(buffer, buf); } -- 2.43.0