From 9e17ac997f921c9de99125a97a0f34ae50f5c498 Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Fri, 14 Feb 2025 13:16:05 +1300 Subject: [PATCH] Remove obsolete comment. Commit 755a4c10d19d prevented StartReadBuffers() from crossing md.c segment boundaries in one operation, but a comment about that possibility remained. --- src/backend/storage/buffer/bufmgr.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/backend/storage/buffer/bufmgr.c b/src/backend/storage/buffer/bufmgr.c index b5938f1b473..80b0d0c5ded 100644 --- a/src/backend/storage/buffer/bufmgr.c +++ b/src/backend/storage/buffer/bufmgr.c @@ -1330,10 +1330,7 @@ StartReadBuffersImpl(ReadBuffersOperation *operation, * StartReadBuffers() were made for the same blocks before * WaitReadBuffers(), only the first would issue the advice. That'd be * a better simulation of true asynchronous I/O, which would only - * start the I/O once, but isn't done here for simplicity. Note also - * that the following call might actually issue two advice calls if we - * cross a segment boundary; in a true asynchronous version we might - * choose to process only one real I/O at a time in that case. + * start the I/O once, but isn't done here for simplicity. */ smgrprefetch(operation->smgr, operation->forknum, -- 2.39.5