Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Dave Page||Date: 2006-07-24 07:31:01|
|Subject: Re: Adding a pgbench run to buildfarm|
|Previous:||From: Jie Zhang||Date: 2006-07-24 06:23:48|
|Subject: Re: On-disk bitmap index patch|
pgsql-patches by date
|Next:||From: Peter Eisentraut||Date: 2006-07-24 09:52:12|
|Subject: Re: Mark change-on-restart-only values in postgresql.conf|
|Previous:||From: Joe Conway||Date: 2006-07-24 06:22:14|
|Subject: Re: Values list-of-targetlists patch for comments (was Re: |