aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/nbtree/nbtutils.c
diff options
context:
space:
mode:
authorDaniel Gustafsson <dgustafsson@postgresql.org>2024-04-18 21:28:07 +0200
committerDaniel Gustafsson <dgustafsson@postgresql.org>2024-04-18 21:28:07 +0200
commit950d4a2cb1d5f427dbccf70dbad510479cc4d8e6 (patch)
tree9991d70c6ff074e92b30a099b8a42ae61aa59818 /src/backend/access/nbtree/nbtutils.c
parentfbed6ebe41beb72d9b7978a414ed4e8515ed1b19 (diff)
downloadpostgresql-950d4a2cb1d5f427dbccf70dbad510479cc4d8e6.tar.gz
postgresql-950d4a2cb1d5f427dbccf70dbad510479cc4d8e6.zip
Fix typos and duplicate words
This fixes various typos, duplicated words, and tiny bits of whitespace mainly in code comments but also in docs. Author: Daniel Gustafsson <daniel@yesql.se> Author: Heikki Linnakangas <hlinnaka@iki.fi> Author: Alexander Lakhin <exclusion@gmail.com> Author: David Rowley <dgrowleyml@gmail.com> Author: Nazir Bilal Yavuz <byavuz81@gmail.com> Discussion: https://postgr.es/m/3F577953-A29E-4722-98AD-2DA9EFF2CBB8@yesql.se
Diffstat (limited to 'src/backend/access/nbtree/nbtutils.c')
-rw-r--r--src/backend/access/nbtree/nbtutils.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/nbtree/nbtutils.c b/src/backend/access/nbtree/nbtutils.c
index 498b8d20358..ecbbc2466d2 100644
--- a/src/backend/access/nbtree/nbtutils.c
+++ b/src/backend/access/nbtree/nbtutils.c
@@ -1756,7 +1756,7 @@ _bt_start_prim_scan(IndexScanDesc scan, ScanDirection dir)
*
* (The rules are the same for backwards scans, except that the operators are
* flipped: just replace the precondition's >= operator with a <=, and the
- * postcondition's <= operator with with a >=. In other words, just swap the
+ * postcondition's <= operator with a >=. In other words, just swap the
* precondition with the postcondition.)
*
* We also deal with "advancing" non-required arrays here. Callers whose
@@ -4133,7 +4133,7 @@ _bt_checkkeys_look_ahead(IndexScanDesc scan, BTReadPageState *pstate,
else
{
/*
- * Failure -- "ahead" tuple is too far ahead (we were too aggresive).
+ * Failure -- "ahead" tuple is too far ahead (we were too aggressive).
*
* Reset the number of rechecks, and aggressively reduce the target
* distance (we're much more aggressive here than we were when the