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 040C711F6942 for ; Tue, 28 Mar 2006 17:15:07 -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 16442-05 for ; Tue, 28 Mar 2006 17:15:03 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 34D2611F6945 for ; Tue, 28 Mar 2006 17:15:01 -0400 (AST) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Tue, 28 Mar 2006 21:15:00 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 28 Mar 2006 15:15:00 -0600 Subject: Re: Bloated pg_shdepend_depender_index From: Scott Marlowe To: Rafael Martinez Cc: "Jim C. Nasby" , pgsql-admin@postgresql.org In-Reply-To: <1143575509.18329.13.camel@linux.site> References: <1143547721.24060.112.camel@bbking.uio.no> <20060328180937.GS75181@pervasive.com> <1143575509.18329.13.camel@linux.site> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1143580500.3625.92.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 28 Mar 2006 15:15:00 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.141 required=5 tests=[AWL=0.140, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.141 X-Spam-Level: X-Archive-Number: 200603/322 X-Sequence-Number: 21079 On Tue, 2006-03-28 at 13:51, Rafael Martinez wrote: > On Tue, 2006-03-28 at 12:09 -0600, Jim C. Nasby wrote: > > > > > Fortunately, you can use Slony to migrate between versions, greatly > > reducing downtime. > > Yes, this is true, but the problem is that if the database is 'big' and > running in an expensive system you need to double your investment only > for the upgrade. > > I am sure we can find another way of doing this that is easier and > faster. Any large, production system should already have replication in place. If not, you're taking your chances with that big system that make any investment questionable. If downtime is a real problem.