X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 104F19FCFDF for ; Mon, 28 Aug 2006 12:28:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 63204-10 for ; Mon, 28 Aug 2006 12:27:57 -0300 (ADT) X-Greylist: delayed 00:48:13.113032 by SQLgrey- Received: from mx.mall.cz (mall--l3sw2-2948.tgnet.cz [82.100.0.98]) by postgresql.org (Postfix) with ESMTP id 31B019FCFD5 for ; Mon, 28 Aug 2006 12:27:55 -0300 (ADT) Received: from localhost (asterix [127.0.0.1]) by mx.mall.cz (Postfix) with ESMTP id AF1A713F60B; Mon, 28 Aug 2006 17:27:54 +0200 (CEST) Received: from mx.mall.cz ([127.0.0.1]) by localhost (asterix [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id 32559-04; Mon, 28 Aug 2006 17:27:52 +0200 (CEST) Message-ID: <44F30B7A.4020800@mall.cz> Date: Mon, 28 Aug 2006 17:27:54 +0200 From: Michal Taborsky - Internet Mall Organization: Internet Mall, a.s. User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Brad Nicholson Cc: pgsql-performance@postgresql.org Subject: Re: Identifying bloated tables References: <44F30022.1000009@mall.cz> <1156776499.10296.5.camel@dba5.int.libertyrms.com> In-Reply-To: <1156776499.10296.5.camel@dba5.int.libertyrms.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at mall.cz X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.365 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/441 X-Sequence-Number: 20626 Brad Nicholson napsal(a): >> I just put together a view, which helps us in indentifying which >> database tables are suffering from space bloat, ie. they take up much > Are you sure you haven't reinvented the wheel? Have you checked out > contrib/pgstattuple ? Well, I wasn't aware of it, so I guess I did reinvent the wheel. I Googled for a solution to this problem, but Googled poorly I suppose. On the other hand, pgstattuple might be a bit difficult to use for not-so-experienced users in answering the question "Which table should I shrink?", as you have to first install it from contrib and then come up with a select to pick the "worst" relations. Anyway, if someone finds this view useful, good. If not, ignore it. Bye. -- Michal Táborský IT operations chief Internet Mall, a.s.