nbtree: Correct inaccurate split location comment.

Minor oversight in commit fab25024338.

diff --git a/src/backend/access/nbtree/nbtsplitloc.c b/src/backend/access/nbtree/nbtsplitloc.c
index fcfc23ce601a33d6a60e0a7de1ea97ae5087d408..ef6dd1cf1920b6b79f47680df44633218d42127a 100644 (file)
--- 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