aboutsummaryrefslogtreecommitdiff
path: root/src/backend/storage/buffer/bufmgr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-03-29 09:13:57 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2023-03-29 09:13:57 -0400
commit58c9600a9f5818f63712ae4262143c42517dcba7 (patch)
tree37e998d858acca5dc39e08d39f51ee27c6aa9561 /src/backend/storage/buffer/bufmgr.c
parent7081ac46ace8c459966174400b53418683c9fe5c (diff)
downloadpostgresql-58c9600a9f5818f63712ae4262143c42517dcba7.tar.gz
postgresql-58c9600a9f5818f63712ae4262143c42517dcba7.zip
Remove empty function BufmgrCommit().
This function has been a no-op for over a decade. Even if bufmgr regains a need to be called during commit, it seems unlikely that the most appropriate call points would be precisely here, so it's not doing us much good as a placeholder either. Now, removing it probably doesn't save any noticeable number of cycles --- but the main call is inside the commit critical section, and the less work done there the better. Matthias van de Meent Discussion: https://postgr.es/m/CAEze2Wi1=tLKbxZnXzcD+8fYKyKqBtivVakLQC_mYBsP4Y8qVA@mail.gmail.com
Diffstat (limited to 'src/backend/storage/buffer/bufmgr.c')
-rw-r--r--src/backend/storage/buffer/bufmgr.c10
1 files changed, 0 insertions, 10 deletions
diff --git a/src/backend/storage/buffer/bufmgr.c b/src/backend/storage/buffer/bufmgr.c
index 95212a39416..fe029d2ea60 100644
--- a/src/backend/storage/buffer/bufmgr.c
+++ b/src/backend/storage/buffer/bufmgr.c
@@ -2789,16 +2789,6 @@ CheckPointBuffers(int flags)
BufferSync(flags);
}
-
-/*
- * Do whatever is needed to prepare for commit at the bufmgr and smgr levels
- */
-void
-BufmgrCommit(void)
-{
- /* Nothing to do in bufmgr anymore... */
-}
-
/*
* BufferGetBlockNumber
* Returns the block number associated with a buffer.