From 3be30d007514d504b1d0554a20527ee5ba7a6cfb Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Tue, 12 Nov 2024 22:09:00 -0500 Subject: [PATCH] Fix obsolete nbtree page reuse FSM comment. Oversight in commit d088ba5a. --- src/backend/access/nbtree/nbtxlog.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/backend/access/nbtree/nbtxlog.c b/src/backend/access/nbtree/nbtxlog.c index b5b0e22447e..7e91584f1ae 100644 --- a/src/backend/access/nbtree/nbtxlog.c +++ b/src/backend/access/nbtree/nbtxlog.c @@ -982,9 +982,9 @@ btree_xlog_newroot(XLogReaderState *record) * As far as any backend operating during original execution is concerned, the * FSM is a cache of recycle-safe pages; the mere presence of the page in the * FSM indicates that the page must already be safe to recycle (actually, - * _bt_getbuf() verifies it's safe using BTPageIsRecyclable(), but that's just - * because it would be unwise to completely trust the FSM, given its current - * limitations). + * _bt_allocbuf() verifies it's safe using BTPageIsRecyclable(), but that's + * just because it would be unwise to completely trust the FSM, given its + * current limitations). * * This isn't sufficient to prevent similar concurrent recycling race * conditions during Hot Standby, though. For that we need to log a -- 2.39.5