From: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp> |
---|---|
To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgstattuple extension for indexes |
Date: | 2006-08-18 02:31:59 |
Message-ID: | 44E5269F.8000004@nttdata.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
ITAGAKI Takahiro wrote:
> Suppose a simple update case, for example, the accounts table in pgbench.
> The default fillfactor of btree indexes is 90%, so the leaf pages are
> fully split after we update 10-20% of tuples. But pgstatindex reports
> the fragmentation is 50% in such condition, but I think we should do
> REINDEX then. My decision came from this.
>
> The setting fillfactor=50% is better than the case with high fillfactor
> but all pages have split once, even if sizes of the indexes are same.
> I worry that users will misunderstand the 50% of fragmentation -- if the
> report says 100%, they'll consider to do REINDEX. But 50%, the necessity
> is unclear.
I think you should use 'average of page density' and 'number of leaf pages'
in such case. It is more useful to know filling condition of the leaves.
I've observed both while running pgbench, and the result is coming with
the WEB+DB PRESS magazine in next Wednesday. :)
Thanks.
--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>
Phone: +81-3-3523-8122
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-08-18 02:39:14 | Re: Can I assume there's only one _RETURN rule? |
Previous Message | ITAGAKI Takahiro | 2006-08-18 02:05:36 | Re: pgstattuple extension for indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-08-18 08:14:47 | Re: [PATCHES] WIP archive_timeout patch |
Previous Message | ITAGAKI Takahiro | 2006-08-18 02:05:36 | Re: pgstattuple extension for indexes |