summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Geoghegan2024-11-13 03:09:00 +0000
committerPeter Geoghegan2024-11-13 03:09:00 +0000
commit3be30d007514d504b1d0554a20527ee5ba7a6cfb (patch)
treef7f0b919638aa84eb4366fcf7a37bbe2a9e1add3
parent93063e2e429b03e8b06295ede0f0ebb5199b656a (diff)
Fix obsolete nbtree page reuse FSM comment.
Oversight in commit d088ba5a.
-rw-r--r--src/backend/access/nbtree/nbtxlog.c6
1 files 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