postgrespro.git / summary / log / commit / refs

commit    bfdbac2ab3ef1a12a7de231552b128ed83ad00bb
Author:   Peter Geoghegan <pg@bowt.ie>
Date:     Mon Jul 15 21:35:06 2019 +0000

    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.


 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 382496d41c..a7882fd874 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];
 	}


[parent: e3899ffd8bea]