From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fillfactor for GIN indexes |
Date: | 2015-02-25 09:20:48 |
Message-ID: | CAPpHfdtWVc0sSwFugo4+tTDwqN=-bN2LxgS=-hnw_mr4LYPcsQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 24, 2015 at 5:15 PM, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
wrote:
> I hoped lowering the fillfactor will improve this, but fillfactor=75 had
> pretty much no effect in this case. Is that expected for this kind of
> workload? I see the previous discussion talked about random updates, not
> inserts, so maybe that's the culprit?
>
Yes. Since posting trees are ordered by item pointers, you can get benefit
of fillfactor only if you use some item pointers lower than item pointers
already in use. You can still get benefit in the insert case but you should
have already some free space in the heap (perhaps do some deletes and
vacuum).
Actually, this is narrowing benefit from GIN fillfactor. Probably, that
means that we should still have default value of 100. But I think GIN
fillfactor still might be useful.
------
With best regards,
Alexander Korotkov.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2015-02-25 09:43:57 | event triggers with args? |
Previous Message | Amit Langote | 2015-02-25 09:20:05 | Re: Partitioning WIP patch (was: Partitioning: issues/ideas) |