diff options
author | Peter Geoghegan <pg@bowt.ie> | 2019-07-15 14:35:06 -0700 |
---|---|---|
committer | Peter Geoghegan <pg@bowt.ie> | 2019-07-15 14:35:06 -0700 |
commit | bfdbac2ab3ef1a12a7de231552b128ed83ad00bb (patch) | |
tree | bfa1027b89c0fa3185a302139ead72685d7f013f | |
parent | e3899ffd8beafdaaa037b503163a9f572e9fc729 (diff) | |
download | postgresql-bfdbac2ab3ef1a12a7de231552b128ed83ad00bb.tar.gz postgresql-bfdbac2ab3ef1a12a7de231552b128ed83ad00bb.zip |
Correct nbtsplitloc.c comment.
The logic just added by commit e3899ffd falls back on a 50:50 page split
in the event of a new item that's just to the right of our provisional
"many duplicates" split point. Fix a comment that incorrectly claimed
that the new item had to be just to the left of our provisional split
point.
Backpatch: 12-, just like commit e3899ffd.
-rw-r--r-- | src/backend/access/nbtree/nbtsplitloc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/nbtree/nbtsplitloc.c b/src/backend/access/nbtree/nbtsplitloc.c index 382496d41cd..a7882fd8742 100644 --- a/src/backend/access/nbtree/nbtsplitloc.c +++ b/src/backend/access/nbtree/nbtsplitloc.c @@ -815,7 +815,7 @@ _bt_bestsplitloc(FindSplitData *state, int perfectpenalty, { /* * Avoid the problem by peforming a 50:50 split when the new item is - * just to the left of the would-be "many duplicates" split point. + * just to the right of the would-be "many duplicates" split point. */ final = &state->splits[0]; } |