| From: | Shaun Thomas <sthomas(at)peak6(dot)com> |
|---|---|
| To: | Venkat Balaji <venkat(dot)balaji(at)verse(dot)in> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, AI Rumman <rummandba(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: REINDEX not working for wastedspace |
| Date: | 2011-09-21 16:30:07 |
| Message-ID: | 4E7A110F.5090901@peak6.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 09/21/2011 11:20 AM, Venkat Balaji wrote:
> It is very important to remove it from the WIKI page.
Removing it is a little premature. :) Definitely going to add a warning
about relying on its output, though. The query itself was created and
integrated into the check_postgres.pl nagios plugin as a very, very
gross estimate of bloated tables.
It wasn't the most accurate thing in the world, but considering what it
had to work with, it did a pretty good job. Generally CLUSTER or VACUUM
FULL would remove a table from the query output, but not always. It's
those edge cases that cause problems.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas(at)peak6(dot)com
______________________________________________
See http://www.peak6.com/email-disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-09-21 16:39:35 | Re: Prepared statements and suboptimal plans |
| Previous Message | Venkat Balaji | 2011-09-21 16:20:08 | Re: REINDEX not working for wastedspace |