sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-13 01:13:08 -04:00
Code Issues Projects Releases Wiki Activity

Fix grammar in GIN README

Browse Source 
Author: Kirill Reshke <reshkekirill@gmail.com>
Discussion: https://postgr.es/m/CALdSSPgu9uAhVYojQ0yjG%3Dq5MaqmiSLUJPhz%2B-u7cA6K6Mc9UA%40mail.gmail.com
This commit is contained in:
Tomas Vondra 2025-03-29 15:14:09 +01:00
parent 8b6a0e2392
commit fb9dff7663
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backend/access/gin/README
View File

@ -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. P_i is grouped with K_{i+1}. -Inf key is not needed.
There are couple of additional notes regarding K_{n+1} key. There are a 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. 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. 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 non-rightmost pages is stored separately and accessed via
GinDataPageGetRightBound(). GinDataPageGetRightBound().