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 C51E09DC9B6 for ; Tue, 28 Mar 2006 08:09:06 -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 22503-04 for ; Tue, 28 Mar 2006 08:09:08 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 4A5F19DC848 for ; Tue, 28 Mar 2006 08:09:04 -0400 (AST) Received: from pat.uio.no (pat.uio.no [129.240.10.6]) by svr4.postgresql.org (Postfix) with ESMTP id 1254D5AF884 for ; Tue, 28 Mar 2006 12:09:01 +0000 (GMT) Received: from mail-mx3.uio.no ([129.240.10.44]) by pat.uio.no with esmtp (Exim 4.43) id 1FOD0F-0007Fh-Da; Tue, 28 Mar 2006 14:08:51 +0200 Received: from bbking.uio.no ([129.240.201.179]) by mail-mx3.uio.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1FOD06-0001PM-GO; Tue, 28 Mar 2006 14:08:42 +0200 Subject: Re: Bloated pg_shdepend_depender_index From: Rafael Martinez Guerrero To: "Jim C. Nasby" Cc: Tom Lane , Peter Eisentraut , pgsql-admin@postgresql.org, Gregory Maxwell In-Reply-To: <20060324164325.GS90527@pervasive.com> References: <27588.1143175698@sss.pgh.pa.us> <200603241150.20021.peter_e@gmx.net> <4553.1143212521@sss.pgh.pa.us> <20060324164325.GS90527@pervasive.com> Content-Type: text/plain Organization: University of Oslo Message-Id: <1143547721.24060.112.camel@bbking.uio.no> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) Date: Tue, 28 Mar 2006 14:08:41 +0200 Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-5.369, required 12, autolearn=disabled, AWL -0.37, UIO_MAIL_IS_INTERNAL -5.00) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.08 required=5 tests=[AWL=0.080] X-Spam-Score: 0.08 X-Spam-Level: X-Archive-Number: 200603/302 X-Sequence-Number: 21059 On Fri, 2006-03-24 at 17:43, Jim C. Nasby wrote: > > Therein lies part of the problem: enough disk space. Now that we're > seeing more and more use of PostgreSQL in data warehousing, it's > becomming less safe to assume you'll have enough disk space to fix bloat > on large tables. Plus I suspect a lot of folks wouldn't be able to > tolerate being locked out of a table for that long (of course that > applies to VACUUM FULL as well...) > Hello Exactly this issue and that you have to make a 'full' dump/restore between major release is a big minus I hear everywhere I explain/discuss about postgres for 24/7 and big databases. It would be wonderful to see a solution to these two 'problems' in the future so postgres becomes an even better product than it is now. -- Rafael Martinez, Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/