Re: Wrong value in metapage of GIN INDEX.

2019-11-05 Thread Moon, Insung
Dear Tom Lane. On Tue, Nov 5, 2019 at 3:55 AM Tom Lane wrote: > > "imai.yoshik...@fujitsu.com" writes: > > Moon-san, kuroda.keisuke-san > > On Thu, Aug 29, 2019 at 8:20 AM, Moon, Insung wrote: > >> The patch is very simple. > >> Fix to increase the value of nEntries only when a non-duplicate GIN

Re: Wrong value in metapage of GIN INDEX.

2019-11-04 Thread Tom Lane
"imai.yoshik...@fujitsu.com" writes: > Moon-san, kuroda.keisuke-san > On Thu, Aug 29, 2019 at 8:20 AM, Moon, Insung wrote: >> 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 le

RE: Wrong value in metapage of GIN INDEX.

2019-10-08 Thread imai.yoshik...@fujitsu.com
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

Re: Wrong value in metapage of GIN INDEX.

2019-08-29 Thread keisuke kuroda
Hi Moon-san. Thank you for posting. We are testing the GIN index onJSONB type. The default maintenance_work_mem (64MB) was fine in usually cases. However, this problem occurs when indexing very large JSONB data. best regards, Keisuke Kuroda 2019年8月29日(木) 17:20 Moon, Insung : > Dear Hackers. >