aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2020-06-29 12:30:39 -0700
committerPeter Geoghegan <pg@bowt.ie>2020-06-29 12:30:39 -0700
commitf7a476f0d656bbc673474b9165cd05fa548c18c9 (patch)
tree41b0cb2af22e1f42cb7b5f7032fcca15548188b2 /src
parent16e3ad5d143795b05a21dc887c2ab384cce4bcb8 (diff)
downloadpostgresql-f7a476f0d656bbc673474b9165cd05fa548c18c9.tar.gz
postgresql-f7a476f0d656bbc673474b9165cd05fa548c18c9.zip
nbtree: Correct inaccurate split location comment.
Minor oversight in commit fab25024338.
Diffstat (limited to 'src')
-rw-r--r--src/backend/access/nbtree/nbtsplitloc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/nbtree/nbtsplitloc.c b/src/backend/access/nbtree/nbtsplitloc.c
index fcfc23ce601..ef6dd1cf192 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