Re: pgstattuple extension for indexes - Mailing list pgsql-patches

From ITAGAKI Takahiro
Subject Re: pgstattuple extension for indexes
Date
Msg-id 20060724144315.699D.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Whole thread Raw
In response to Re: pgstattuple extension for indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgstattuple extension for indexes  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: pgstattuple extension for indexes  ("Satoshi Nagayasu" <nagayasus@nttdata.co.jp>)
List pgsql-patches
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> >> Also, I added an experimental feature for btree indexes. It checks
> >> fragmentation factor of indexes.

> The really serious problem with reporting this info via NOTICE is that
> there's no way for a program to get its hands on the info.  The output
> tuple format needs to be extended instead.

Ok, I added 'fragmented_percent' field to the output tuple. This
information will help us to decide when to do REINDEX.
However, it is only avaliable for btree index presently. Other indexes
should have equivalent information, but I don't know how to determine it.


BTW, should we change VACUUM VERBOSE in the same way? If we do so,
autovacuum can handle the reports of VACUUM VERBOSE and plan when to
do VACUUM FULL, REINDEX and/or CLUSTER using the information.
Is this worth doing?

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center


Attachment

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: Values list-of-targetlists patch for comments (was Re:
Next
From: Peter Eisentraut
Date:
Subject: Re: Mark change-on-restart-only values in postgresql.conf