aboutsummaryrefslogtreecommitdiff
path: root/src/include/access/gist.h
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-11-14 11:43:10 +0900
committerMichael Paquier <michael@paquier.xyz>2020-11-14 11:43:10 +0900
commit788dd0b839fc9f2c85caf86014105afdb60ed5e3 (patch)
tree18e85b6a2483e0a513cd9b114abef92caf1c9c1d /src/include/access/gist.h
parentec0294fb2c8287fd673c57701cdcf6c6396b2f60 (diff)
downloadpostgresql-788dd0b839fc9f2c85caf86014105afdb60ed5e3.tar.gz
postgresql-788dd0b839fc9f2c85caf86014105afdb60ed5e3.zip
Fix some typos
Author: Daniel Gustafsson Discussion: https://postgr.es/m/C36ADFDF-D09A-4EE5-B186-CB46C3653F4C@yesql.se
Diffstat (limited to 'src/include/access/gist.h')
-rw-r--r--src/include/access/gist.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/include/access/gist.h b/src/include/access/gist.h
index 4f6dae9a76b..14b1190cd7e 100644
--- a/src/include/access/gist.h
+++ b/src/include/access/gist.h
@@ -80,7 +80,7 @@ typedef GISTPageOpaqueData *GISTPageOpaque;
* Maximum possible sizes for GiST index tuple and index key. Calculation is
* based on assumption that GiST page should fit at least 4 tuples. In theory,
* GiST index can be functional when page can fit 3 tuples. But that seems
- * rather inefficent, so we use a bit conservative estimate.
+ * rather inefficient, so we use a bit conservative estimate.
*
* The maximum size of index key is true for unicolumn index. Therefore, this
* estimation should be used to figure out which maximum size of GiST index key