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 866979DCBD3 for ; Fri, 24 Mar 2006 00:48:21 -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 09891-07 for ; Fri, 24 Mar 2006 00:48:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 5996B9DCAAB for ; Fri, 24 Mar 2006 00:48:19 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k2O4mI92027589; Thu, 23 Mar 2006 23:48:18 -0500 (EST) To: "Gregory Maxwell" cc: pgsql-admin@postgresql.org Subject: Re: Bloated pg_shdepend_depender_index In-reply-to: References: <20060324023105.GB11242@surnet.cl> <21266.1143170652@sss.pgh.pa.us> Comments: In-reply-to "Gregory Maxwell" message dated "Thu, 23 Mar 2006 22:58:11 -0500" Date: Thu, 23 Mar 2006 23:48:18 -0500 Message-ID: <27588.1143175698@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.114 required=5 tests=[AWL=0.114] X-Spam-Score: 0.114 X-Spam-Level: X-Archive-Number: 200603/229 X-Sequence-Number: 20986 "Gregory Maxwell" writes: > So it's by design that these now bloated index won't shrink if let > unvacuumed? I didn't expect to hit something like that. 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. regards, tom lane