aboutsummaryrefslogtreecommitdiff
path: root/src/include/lib
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-02-06 11:33:58 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-02-06 11:33:58 +0200
commit181bdb90ba1f2361aec5a621c8f1e01736f8cad2 (patch)
tree00678950791dcd1b312418e51b46582a3c9a8b79 /src/include/lib
parent9863017b87f3592ff663d03fc663a4f1f8fdb8b2 (diff)
downloadpostgresql-181bdb90ba1f2361aec5a621c8f1e01736f8cad2.tar.gz
postgresql-181bdb90ba1f2361aec5a621c8f1e01736f8cad2.zip
Fix typos in comments.
Backpatch to all supported versions, where applicable, to make backpatching of future fixes go more smoothly. Josh Soref Discussion: https://www.postgresql.org/message-id/CACZqfqCf+5qRztLPgmmosr-B0Ye4srWzzw_mo4c_8_B_mtjmJQ@mail.gmail.com
Diffstat (limited to 'src/include/lib')
-rw-r--r--src/include/lib/simplehash.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/include/lib/simplehash.h b/src/include/lib/simplehash.h
index 12aedbc384c..72e18499c07 100644
--- a/src/include/lib/simplehash.h
+++ b/src/include/lib/simplehash.h
@@ -345,7 +345,7 @@ SH_GROW(SH_TYPE *tb, uint32 newsize)
* we need. We neither want tb->members increased, nor do we need to do
* deal with deleted elements, nor do we need to compare keys. So a
* special-cased implementation is lot faster. As resizing can be time
- * consuming and frequent, that's worthwile to optimize.
+ * consuming and frequent, that's worthwhile to optimize.
*
* To be able to simply move entries over, we have to start not at the
* first bucket (i.e olddata[0]), but find the first bucket that's either
@@ -620,7 +620,7 @@ SH_DELETE(SH_TYPE *tb, SH_KEY_TYPE key)
/*
* Backward shift following elements till either an empty element
- * or an element at its optimal position is encounterered.
+ * or an element at its optimal position is encountered.
*
* While that sounds expensive, the average chain length is short,
* and deletions would otherwise require toombstones.