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 CDAD611F6213 for ; Tue, 28 Mar 2006 19:03:35 -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 32480-09 for ; Tue, 28 Mar 2006 19:03:34 -0400 (AST) X-Greylist: delayed 10:54:35.31401 by SQLgrey- Received: from pat.uio.no (pat.uio.no [129.240.10.6]) by postgresql.org (Postfix) with ESMTP id 2403C11F6251 for ; Tue, 28 Mar 2006 19:03:32 -0400 (AST) Received: from mail-mx4.uio.no ([129.240.10.45]) by pat.uio.no with esmtp (Exim 4.43) id 1FONDm-0004rN-Gk; Wed, 29 Mar 2006 01:03:30 +0200 Received: from ti200710a080-3004.bb.online.no ([85.164.139.188] helo=[10.1.1.101]) by mail-mx4.uio.no with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.43) id 1FONDi-0002jr-NJ; Wed, 29 Mar 2006 01:03:26 +0200 Subject: Re: Bloated pg_shdepend_depender_index From: Rafael Martinez To: Scott Marlowe Cc: "Jim C. Nasby" , pgsql-admin@postgresql.org In-Reply-To: <1143580500.3625.92.camel@state.g2switchworks.com> References: <1143547721.24060.112.camel@bbking.uio.no> <20060328180937.GS75181@pervasive.com> <1143575509.18329.13.camel@linux.site> <1143580500.3625.92.camel@state.g2switchworks.com> Content-Type: text/plain Organization: University of Oslo Date: Wed, 29 Mar 2006 01:05:59 +0200 Message-Id: <1143587159.18329.56.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=-3.907, required 12, autolearn=disabled, AWL 1.09, 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/325 X-Sequence-Number: 21082 On Tue, 2006-03-28 at 15:15 -0600, Scott Marlowe wrote: > 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. You do not need replication in place to run a large system in a responsible way. I agree that you need redundance in many layers but you have to stop at some point. We have for example, some big/expensive disk arrays in our system that have a lot of redundancy, redundant hot plug power supplies, redundant hot plug blowers, redundant hot plug cache batteries, redundant hot plug FC I/O modules, redundant pair of controllers, etc, etc and an expensive 24x7 onsite hardware support. But we do not have an extra disk array just in case the one in production stops working (it can happen but we have to trust it won't) Fast scsi disks in this type of array are not cheap, and the bosses are not happy if you say that you need the double of space to upgrade the system, this can be very expensive in a big system. I work with postgresql every day and I am very happy with it, but this does not mean I can not see the issues that could be improve to have a even better open source DBMS. And I think in my humble opinion that bloated indexes + better upgrade procedures between major releases are two things that should get improved in the future. regards, -- Rafael Martinez, Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/