Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 388179FB57A for ; Wed, 4 Apr 2007 10:48:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 34695-02-2 for ; Wed, 4 Apr 2007 10:48:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from heaven.kostyrka.org (h1634.serverkompetenz.net [81.169.154.44]) by postgresql.org (Postfix) with ESMTP id 3A57C9FB6FE for ; Wed, 4 Apr 2007 10:48:44 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by heaven.kostyrka.org (Postfix) with ESMTP id D264C4FB8C; Wed, 4 Apr 2007 15:48:39 +0200 (CEST) Received: from heaven.kostyrka.org ([127.0.0.1]) by localhost (heaven.kostyrka.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16741-10; Wed, 4 Apr 2007 15:48:39 +0200 (CEST) Received: from andi-lap (localhost [127.0.0.1]) by heaven.kostyrka.org (Postfix) with SMTP id 744D84FB88; Wed, 4 Apr 2007 15:48:37 +0200 (CEST) Received: by andi-lap (sSMTP sendmail emulation); Wed, 4 Apr 2007 15:48:40 +0200 Date: Wed, 4 Apr 2007 15:48:40 +0200 From: Andreas Kostyrka To: Peter Kovacs , "david@lang.hm" , Geoff Tolley , Ron , "jason@ohloh.net" , pgsql-performance@postgresql.org Subject: Re: SCSI vs SATA Message-ID: <20070404134839.GI20893@andi-lap.la.revver.com> References: <9C0858F5-0A48-4AF9-80FF-E4BA14F0F965@ohloh.net> <4613053F.5070401@polimetrix.com> <20070404124640.GC20893@andi-lap.la.revver.com> <20070404131920.GA8549@alvh.no-ip.org> <20070404133620.GD8549@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070404133620.GD8549@alvh.no-ip.org> User-Agent: mutt-ng/devel-r804 (Debian) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/66 X-Sequence-Number: 23943 * Alvaro Herrera [070404 15:42]: > Peter Kovacs escribió: > > But if an individual disk fails in a disk array, sooner than later you > > would want to purchase a new fitting disk, walk/drive to the location > > of the disk array, replace the broken disk in the array and activate > > the new disk. Is this correct? > > Ideally you would have a spare disk to let the array controller replace > the broken one as soon as it breaks, but yeah, that would be more or Well, no matter what, you need to test this procedure. I'd expect in many cases the disc io during the rebuild of the array to that much slower that the database server won't be able to cope with the load. Andreas