postgres.git / summary / log / commit / refs

commit    e8c334c47abb6c8f648cb50241c2cd65c9e4e6dc
Author:   Alexander Korotkov <akorotkov@postgresql.org>
Date:     Sat Oct 07 08:55:17 2023 +0000

    Fix typos in e0b1ee17dc
    
    Reported-by: Alexander Lakhin


 src/backend/access/nbtree/nbtsearch.c | 2 +-
 src/backend/access/nbtree/nbtutils.c  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/backend/access/nbtree/nbtsearch.c b/src/backend/access/nbtree/nbtsearch.c
index c47eaed0e98..288c6915864 100644
--- a/src/backend/access/nbtree/nbtsearch.c
+++ b/src/backend/access/nbtree/nbtsearch.c
@@ -1665,7 +1665,7 @@ _bt_readpage(IndexScanDesc scan, ScanDirection dir, OffsetNumber offnum)
 			/*
 			 * If the result of prechecking required keys was true, then in
 			 * assert-enabled builds we also recheck that _bt_checkkeys()
-			 * result is is the same.
+			 * result is the same.
 			 */
 			Assert(!requiredMatchedByPrecheck ||
 				   passes_quals == _bt_checkkeys(scan, itup, indnatts, dir,
diff --git a/src/backend/access/nbtree/nbtutils.c b/src/backend/access/nbtree/nbtutils.c
index 8e9c892f78a..1510b97fbe1 100644
--- a/src/backend/access/nbtree/nbtutils.c
+++ b/src/backend/access/nbtree/nbtutils.c
@@ -1415,7 +1415,7 @@ _bt_checkkeys(IndexScanDesc scan, IndexTuple tuple, int tupnatts,
 
 		/*
 		 * Is the key required for scanning for either forward or backward
-		 * direction?  If so and called told us that these types of keys are
+		 * direction?  If so and caller told us that these types of keys are
 		 * known to be matched, skip the check.  Except for the row keys,
 		 * where NULLs could be found in the middle of matching values.
 		 */


[parent: ffb69b23115a]