X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id ECA1F9DC83F for ; Fri, 24 Mar 2006 06:58:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76580-09 for ; Fri, 24 Mar 2006 06:58:30 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id B7B429DC846 for ; Fri, 24 Mar 2006 06:58:26 -0400 (AST) Received: from bell.credativ.de (p50894CFD.dip.t-dialin.net [80.137.76.253]) (using TLSv1 with cipher EXP1024-RC4-SHA (56/128 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id A1499D75FB; Fri, 24 Mar 2006 11:58:27 +0100 (CET) From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: Bloated pg_shdepend_depender_index Date: Fri, 24 Mar 2006 11:50:19 +0100 User-Agent: KMail/1.8.3 Cc: Tom Lane , "Gregory Maxwell" References: <27588.1143175698@sss.pgh.pa.us> In-Reply-To: <27588.1143175698@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200603241150.20021.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.106 required=5 tests=[AWL=0.106] X-Spam-Score: 0.106 X-Spam-Level: X-Archive-Number: 200603/231 X-Sequence-Number: 20988 Am Freitag, 24. März 2006 05:48 schrieb Tom Lane: > Well, the VACUUM FULL algorithm is incapable of shrinking indexes --- > the only way is REINDEX, or something else that reconstructs indexes > from scratch, such as CLUSTER. One of the things we need to look into > is putting more smarts into VACUUM so that it automatically does > something reasonable when faced with extreme cases like these. If the user is running VACUUM FULL, he has presumably determined that the table is too bloated to be recovered in a graceful way, and quite likely the indexes are going to be bloated similarly. So seemingly one might as well launch a reindexing on the table after VACUUM FULL has done its thing. Whether that should be automatic is another question but perhaps the advice should be documented somewhere? -- Peter Eisentraut http://developer.postgresql.org/~petere/