RE: Wrong value in metapage of GIN INDEX.
От | imai.yoshikazu@fujitsu.com |
---|---|
Тема | RE: Wrong value in metapage of GIN INDEX. |
Дата | |
Msg-id | OSAPR01MB4609CF4DD8BEEC07EDDAE190949A0@OSAPR01MB4609.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | Wrong value in metapage of GIN INDEX. ("Moon, Insung" <tsukiwamoon.pgsql@gmail.com>) |
Ответы |
Re: Wrong value in metapage of GIN INDEX.
|
Список | pgsql-hackers |
Moon-san, kuroda.keisuke-san On Thu, Aug 29, 2019 at 8:20 AM, Moon, Insung wrote: > =# CREATE INDEX foo_idx ON foo USING gin (i jsonb_ops); > =# SELECT * FROM gin_metapage_info(get_raw_page('foo_idx', 0)) WITH (fastupdate=off); This is not important thing but some mistakes are here. =# CREATE INDEX foo_idx ON foo USING gin (i jsonb_ops) WITH (fastupdate=off); =# SELECT * FROM gin_metapage_info(get_raw_page('foo_idx', 0)); > In this example, the nentries value should be 10001 because the gin index stores duplicate values in one leaf(posting > tree or posting list). ... > The patch is very simple. > Fix to increase the value of nEntries only when a non-duplicate GIN index leaf added. Does nentries show the number of entries in the leaf pages? If so, the fix seems to be correct. -- Yoshikazu Imai
В списке pgsql-hackers по дате отправления: