postgres.git / summary / log / commit / refs

commit    3eec0e65331e4a38d0c8b3ac251ea3885452fd71
Author:   Nathan Bossart <nathan@postgresql.org>
Date:     Tue Aug 19 21:48:22 2025 +0000

    Fix comment for MAX_SIMUL_LWLOCKS.
    
    This comment mentions that pg_buffercache locks all buffer
    partitions simultaneously, but it hasn't done so since v10.
    
    Oversight in commit 6e654546fb.
    
    Reviewed-by: Andres Freund <andres@anarazel.de>
    Discussion: https://postgr.es/m/aKTuAHVEuYCUmmIy%40nathan


 src/backend/storage/lmgr/lwlock.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/backend/storage/lmgr/lwlock.c b/src/backend/storage/lmgr/lwlock.c
index ec9c345ffdf..c80b43f1f55 100644
--- a/src/backend/storage/lmgr/lwlock.c
+++ b/src/backend/storage/lmgr/lwlock.c
@@ -162,8 +162,7 @@ LWLockPadded *MainLWLockArray = NULL;
 /*
  * We use this structure to keep track of locked LWLocks for release
  * during error recovery.  Normally, only a few will be held at once, but
- * occasionally the number can be much higher; for example, the pg_buffercache
- * extension locks all buffer partitions simultaneously.
+ * occasionally the number can be much higher.
  */
 #define MAX_SIMUL_LWLOCKS	200
 


[parent: eab9e4e27c0c]