Satoshi Nagayasu <[EMAIL PROTECTED]> wrote:
> Well, in that way, following two conditions,
> [1] [x] [2] [y] [3]
> and
> [3] [x] [2] [y] [1]
> will be calculated as same fragmentation ratio(100%), I can't agree
> with that, because both will generate different costs while index scan
> in the real world (I don't care about page splitting algorithm now).
I think the calculations (100%) are appropriate, because we should do
REINDEX in both case. Supposing to the sizes of [x], [y] are mega or giga
bytes, the order is not important; we have to do large seeks in both case.
In addition, the latter case rarely happens in real world, isn't it?
> However, in such way, if I get '57.6%' as a fragmentation radio,
> what does it mean? What can I do next?
I think the information of fragmentations are probably not
the most important; the information users want to know are
"When to do REINDEX?" and "How to set the fillfactor?".
I hope you to write how to interpret the framgentation (and other) info
in README. In my understanding, I'll write "You'd better do REINDEX when
you see the fragmentation is greater than 50%" under the present
calculation method.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
