From f7a476f0d656bbc673474b9165cd05fa548c18c9 Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Mon, 29 Jun 2020 12:30:39 -0700 Subject: [PATCH] nbtree: Correct inaccurate split location comment. Minor oversight in commit fab25024338. --- src/backend/access/nbtree/nbtsplitloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/access/nbtree/nbtsplitloc.c b/src/backend/access/nbtree/nbtsplitloc.c index fcfc23ce60..ef6dd1cf19 100644 --- a/src/backend/access/nbtree/nbtsplitloc.c +++ b/src/backend/access/nbtree/nbtsplitloc.c @@ -190,7 +190,7 @@ _bt_findsplitloc(Relation rel, Assert(!BTreeTupleIsPosting(newitem)); /* - * maxsplits should never exceed maxoff because there will be at most as + * nsplits should never exceed maxoff because there will be at most as * many candidate split points as there are points _between_ tuples, once * you imagine that the new item is already on the original page (the * final number of splits may be slightly lower because not all points