Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 993199FA373 for ; Mon, 11 Dec 2006 05:51:49 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 12831-03 for ; Mon, 11 Dec 2006 05:51:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 9063B9FA344 for ; Mon, 11 Dec 2006 05:51:40 -0400 (AST) thread-index: AccdCfc778EylL65Rei/KO0NjCbf2Q== Received: from [192.168.0.20] ([84.12.196.220]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Dec 2006 04:51:43 -0500 Subject: Re: Recovery plan for DRDB setup - recovery tool From: "Simon Riggs" To: "Morten Andersen" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 Content-Class: urn:content-classes:message Importance: normal Cc: In-Reply-To: <4577E080.4060705@instadia.net> References: <4577E080.4060705@instadia.net> Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 11 Dec 2006 09:51:01 +0000 Message-ID: <1165830662.3839.886.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Dec 2006 09:51:43.0843 (UTC) FILETIME=[F6F3C330:01C71D09] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/144 X-Sequence-Number: 23936 On Thu, 2006-12-07 at 09:36 +0000, Morten Andersen wrote: > Our initial tests also shows that the failovers are problem free. But > we > would like to have a plan for how to handle the case where a failover > fails. With respect to DRBD, you'd need to look at how that works specifically since it isn't part of the basic distrubution. > So are there any Postgresql tools for analyzing and repairing the > "offline" database files (like e.g. the MySQL 'myisamchk'-tool). Or > are > there only "online" tools like 'vacuumdb --full --analyze'. The philosophy is different. PostgreSQL tries to bring up your database and make it available as quickly as possible, even after a crash. The checking of any changed data blocks is performed automatically during recovery - so no need to run a manual tool while the server is down. The idea that you'd need a checking tool comes from not trusting your database. The PostgreSQL way is to ensure you don't lose that trust because there are no short-cuts and leaps of faith taken to make the database go faster. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com