From 4c13e172d5ddfbdac412f4247e3e049d075b7699 Mon Sep 17 00:00:00 2001 From: reshke kirill Date: Tue, 3 Dec 2024 15:02:47 +0000 Subject: [PATCH v37 3/7] Fix wording in GIN README. --- src/backend/access/gin/README | 6 +++--- 1 file 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(). -- 2.43.0