database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-17 17:02:08 +03:00
Code Activity

Remove obsolete comment.

Browse Source 
Commit 755a4c10d1 prevented StartReadBuffers() from crossing md.c
segment boundaries in one operation, but a comment about that
possibility remained.
This commit is contained in:
Thomas Munro
2025-02-14 13:16:05 +13:00
parent 432c30dc4e
commit 9e17ac997f
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/storage/buffer/bufmgr.c
View File

@ -1330,10 +1330,7 @@ StartReadBuffersImpl(ReadBuffersOperation *operation,
* StartReadBuffers() were made for the same blocks before * StartReadBuffers() were made for the same blocks before
* WaitReadBuffers(), only the first would issue the advice. That'd be * WaitReadBuffers(), only the first would issue the advice. That'd be
* a better simulation of true asynchronous I/O, which would only * 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 * start the I/O once, but isn't done here for simplicity.
* 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.
*/ */
smgrprefetch(operation->smgr, smgrprefetch(operation->smgr,
operation->forknum, operation->forknum,