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 75E6A11F6927 for ; Tue, 28 Mar 2006 16:44:12 -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 12169-01 for ; Tue, 28 Mar 2006 16:44:08 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 0552711F6901 for ; Tue, 28 Mar 2006 16:44:07 -0400 (AST) Received: from pat.uio.no (pat.uio.no [129.240.10.6]) by svr4.postgresql.org (Postfix) with ESMTP id 0CD9A5B0005 for ; Tue, 28 Mar 2006 19:53:02 +0000 (GMT) Received: from mail-mx3.uio.no ([129.240.10.44]) by pat.uio.no with esmtp (Exim 4.43) id 1FOKBo-0001nO-Ku; Tue, 28 Mar 2006 21:49:16 +0200 Received: from ti200710a080-3004.bb.online.no ([85.164.139.188] helo=[10.1.1.101]) by mail-mx3.uio.no with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.43) id 1FOKBm-0001cy-85; Tue, 28 Mar 2006 21:49:14 +0200 Subject: Re: Bloated pg_shdepend_depender_index From: Rafael Martinez To: "Jim C. Nasby" Cc: pgsql-admin@postgresql.org In-Reply-To: <20060328180937.GS75181@pervasive.com> References: <1143547721.24060.112.camel@bbking.uio.no> <20060328180937.GS75181@pervasive.com> Content-Type: text/plain Organization: University of Oslo Date: Tue, 28 Mar 2006 21:51:49 +0200 Message-Id: <1143575509.18329.13.camel@linux.site> Mime-Version: 1.0 X-Mailer: Evolution 2.4.0 Content-Transfer-Encoding: 7bit X-UiO-Spam-info: not spam, SpamAssassin (score=-4.069, required 12, autolearn=disabled, AWL 0.93, UIO_MAIL_IS_INTERNAL -5.00) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200603/320 X-Sequence-Number: 21077 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. -- Rafael Martinez, Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/