Search Postgresql Archives

Re: FILLFACTOR and increasing index

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


I've studied the implementation of the btree indexes and how exactly the
fillfactor is used, and in general

- when a page split happens, the process needs to obtain more locks
  than with simple insert, which may result in contention with other
  processes that modify the index (the same pages)

- the fillfactor is used only for the leaf pages, the rest of the index
  does not use it (directly)

So lowering the number of page splits might remove some contention when
there's a lot of processes accessing the same pages.

But that's the theory - I really was not able to come up with a test
that benefits from lower fillfactor. Actually the lower the fillfactor,
the larger the index, which may be a significant issue with huge indexes.

So in your case, I'd probably go with the default fillfactor (90), and
maybe I'd consider even using fillfactor=100, to make the index as dense
as possible.

Anyway I guess the impact of this will be negligible, compared to other
parameters (shared buffers, work_mem, etc.).


Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:

[Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Programming PHP]     [Kernel Newbies]     [PHP Classes]     [Find Someone Nice]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux