Postgres Pro
Downloads
Home   >   mailing lists

Negative imact of maintenance_work_mem to GIN size - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Negative imact of maintenance_work_mem to GIN size
Date
Msg-id CAPpHfdt8Yxbj9sJ_9V15Rne1qu08+F+HFnvqceYuVxLXev42ww@mail.gmail.com
Whole thread Raw
Responses Re: Negative imact of maintenance_work_mem to GIN size  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
Tree view
Hi!

I found that sometimes larger maintenance_work_mem leads to larger GIN index. That is quite strange. ISTM that it's related to posting lists compression but I can't figure out how exactly it is.

See example on delicious bookmarks dataset.


set maintenance_work_mem = '1GB';
create index js_idx1 on js using gin(v jsonb_path_idx);
set maintenance_work_mem = '16MB';
create index js_idx2 on js using gin(v jsonb_path_ops);

                        List of relations
 Schema |  Name   | Type  | Owner  | Table |  Size  | Description
--------+---------+-------+--------+-------+--------+-------------
 public | js_idx1 | index | smagen | js    | 432 MB |
 public | js_idx2 | index | smagen | js    | 309 MB |
(2 rows)

------
With best regards,
Alexander Korotkov.

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: buildfarm animals and 'snapshot too old'
Next
From: Tom Lane
Date:
Subject: Re: buildfarm animals and 'snapshot too old'