summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTomas Vondra2025-03-29 14:14:09 +0000
committerTomas Vondra2025-03-29 14:14:25 +0000
commitfb9dff76635d4c32198f30a3cb503588d557d156 (patch)
treec367e22a4505919fba4857dd5b7cf08b57c95aee
parent8b6a0e2392b9fc3f9b821da705797bb54c982dc1 (diff)
Fix grammar in GIN README
Author: Kirill Reshke <[email protected]> Discussion: https://postgr.es/m/CALdSSPgu9uAhVYojQ0yjG%3Dq5MaqmiSLUJPhz%2B-u7cA6K6Mc9UA%40mail.gmail.com
-rw-r--r--src/backend/access/gin/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/access/gin/README b/src/backend/access/gin/README
index b0807316212..742bcbad499 100644
--- a/src/backend/access/gin/README
+++ b/src/backend/access/gin/README
@@ -237,10 +237,10 @@ GIN packs keys and downlinks into tuples in a different way.
P_i is grouped with K_{i+1}. -Inf key is not needed.
-There are couple of additional notes regarding K_{n+1} key.
-1) In entry tree rightmost page, a key coupled with P_n doesn't really matter.
+There are a couple of additional notes regarding K_{n+1} key.
+1) In the entry tree on the rightmost page, a key coupled with P_n doesn't really matter.
Highkey is assumed to be infinity.
-2) In posting tree, a key coupled with P_n always doesn't matter. Highkey for
+2) In the posting tree, a key coupled with P_n always doesn't matter. Highkey for
non-rightmost pages is stored separately and accessed via
GinDataPageGetRightBound().