Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id A312CB5DC09 for ; Wed, 21 Sep 2011 13:30:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 05733-02 for ; Wed, 21 Sep 2011 16:30:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from smtp2.peak6.com (smtp2.peak6.com [38.98.137.9]) by mail.postgresql.org (Postfix) with ESMTP id 74A03B5DC29 for ; Wed, 21 Sep 2011 13:30:09 -0300 (ADT) X-AuditID: 0a02cb1e-b7bf4ae000000d2a-d9-4e7a11115aea Message-ID: <4E7A110F.5090901@peak6.com> Date: Wed, 21 Sep 2011 11:30:07 -0500 From: Shaun Thomas Reply-To: Organization: Peak6 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Venkat Balaji CC: Tom Lane , AI Rumman , Subject: Re: REINDEX not working for wastedspace References: <4E79E702.4090405@peak6.com> <22059.1316614372@sss.pgh.pa.us> <4E79FAEA.8090100@peak6.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.220.61] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOIsWRmVeSWpSXmKPExsXCxcQrpiskWOVnsPggu8X1meeYLT70Blic WnWXyWLR47UsDiweO2fdZfe4sG8au8eiZxtZPCY9mMIWwBLVwGiTmJeXX5JYkqqQklqcbKsU 4OrobaYQXJKYl5JYlKLgklmcnJOYmZtapKSQmWKrZKSkUJCTmJyam5pXYquUWFCQmpeiZMel gAFsgMoy8xRS85LzUzLz0m2VPIP9dS0sTC11DZXs4hEgoZsl4+zMJsaCZ6wVbYu+sjYwnmXp YuTkkBAwkTg3vZ0NwhaTuHBvPZjNK6AhMX/mQkYQm0VAVeLYsUdMIDabgJrEwt03weJCArIS +1edYwWx+QWEJfZ9aGIGsUUFAiQWTHrLCDFHUOLkzCdgu0QEtCSOHL0MFOfgYBZIl1i+wREk LCxgJTH/+hqgMBfQyA+MEjsa/oHN5BQIlDh58QPYTGYBW4kLc66zQNjyEtvfzmGGuEFO4k7D czaQmRICChLXl/tPYBSahWTzLCTds5B0L2BkXsUoXlyWmJyRaVZQnFtSYKhXkJqYbaaXl1qy iREc3afldjCuuKB4iFGAg1GJh3fCsQo/IdbEsuLK3EOMEhzMSiK8/Xcq/YR4UxIrq1KL8uOL SnNSiw8xagODbCKzFHdyPjDx5JXEGxsYKInzJv3J9BMSSAemgezU1ILUIphqJg5OqQbGztO3 phZWqqfP7Z4bLdwU3tT7OyIvI+wA03U571/PDT5MdnlVGryg4b900h2HD1PfTy5+evmL+bfp Rwz9r80ImOhaekpy1UnlM5ZzjEJPxWQdvrGlVu3OTv+lp/uSuaNDF3fG8TZXSn2VPrPIYnqy CvOFfUZtV5X2zzEJX9N7syD96Js/UxekKrEUZyQaajEXFScCAKIuW5j6AgAA X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201109/332 X-Sequence-Number: 45108 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