From: | Peter Bex <Peter(dot)Bex(at)xs4all(dot)nl> |
---|---|
To: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Tuple storage overhead |
Date: | 2010-04-16 10:13:27 |
Message-ID: | 20100416101327.GF11616@frohike.homeunix.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Apr 16, 2010 at 11:59:38AM +0200, Szymon Guz wrote:
> File pages are not fully filled from the start as that could result in bad
> performance of queries later.
The manual page you linked to says something else:
"The fillfactor for a table is a percentage between 10 and 100.
100 (complete packing) is the default."
However, the index has a default fill factor of 90, so I guess
I can tweak that to 100 to shave off another few percent.
(there will be no updates nor extra inserts on these tables)
Thanks for the tip! I hope there are more ways to tweak it, though
because this doesn't save that much.
Regards,
Peter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
is especially attractive, not only because it can be economically
and scientifically rewarding, but also because it can be an aesthetic
experience much like composing poetry or music."
-- Donald Knuth
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-04-16 10:18:23 | Re: tar error, in pg_start_backup() |
Previous Message | Szymon Guz | 2010-04-16 09:59:38 | Re: Tuple storage overhead |