From: Shaun Thomas <sthomas@peak6.com>
To: Venkat Balaji <venkat.balaji@verse.in>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: AI Rumman <rummandba@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: REINDEX not working for wastedspace
Date: Wed, 21 Sep 2011 11:30:07 -0500
Message-ID: <4E7A110F.5090901@peak6.com> (raw)
In-Reply-To: <CAFrxt0jW890QpvGNscao4a_pe9KEQKMyMrJwAxE2dMPuaey=Wg@mail.gmail.com>
References: <CAGoODpcBxGLyF=bY3_5opO4YckgJqFGwBxveU_cYsrXBbN4NgQ@mail.gmail.com>
<4E79E702.4090405@peak6.com>
<22059.1316614372@sss.pgh.pa.us>
<4E79FAEA.8090100@peak6.com>
<CAFrxt0jW890QpvGNscao4a_pe9KEQKMyMrJwAxE2dMPuaey=Wg@mail.gmail.com>
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@peak6.com
______________________________________________
See http://www.peak6.com/email-disclaimer/ for terms and conditions related to this email
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@peak6.com, venkat.balaji@verse.in, tgl@sss.pgh.pa.us, rummandba@gmail.com
Subject: Re: REINDEX not working for wastedspace
In-Reply-To: <4E7A110F.5090901@peak6.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox