Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 2917B9F9FB2 for ; Fri, 8 Dec 2006 05:42:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 23014-09 for ; Fri, 8 Dec 2006 05:42:15 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail.instadia.net (mail.instadia.net [80.165.96.2]) by postgresql.org (Postfix) with ESMTP id DC67F9F9F46 for ; Fri, 8 Dec 2006 05:42:29 -0400 (AST) Received: from [10.0.0.14] (dev8.instadia.net [10.0.0.14]) by mail.instadia.net (Postfix) with ESMTP id 3213BD56C8; Fri, 8 Dec 2006 10:42:28 +0100 (CET) Message-ID: <45793383.2090505@instadia.net> Date: Fri, 08 Dec 2006 09:42:27 +0000 From: Morten Andersen User-Agent: Debian Thunderbird 1.0.2 (X11/20060926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Recovery plan for DRDB setup - recovery tool References: <4577E080.4060705@instadia.net> <200612071403.27722.peter_e@gmx.net> In-Reply-To: <200612071403.27722.peter_e@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50 X-Spam-Level: X-Archive-Number: 200612/59 X-Sequence-Number: 23851 Hi Peter, Peter Eisentraut wrote: > Morten Andersen wrote: > >>So are there any Postgresql tools for analyzing and repairing the >>"offline" database files (like e.g. the MySQL 'myisamchk'-tool). > > > No. > > >>So, how do other DRDB Postgresql sites handles failovers. Do you do >>anything pro-active on the slave before starting Postgresql, or do >>you trust DRDB and Postgresql completely. > > > If you don't trust PostgreSQL, why would you trust its offline recovery > tools? :-) - sorry, I probably misphrased the question a little. It is not really Postgresql I don't trust. It is more the combination of HW on two machines, network and DRDB. And it is not really an issue about not trusting any of the components involved, but about knowing what to do if we ever find us self with a group of erroneous DB files. But since you answered that no offline tools exist, and due to phrases like this: ".. Since the postmaster can now clean up by itself, it is unlikely that ipcclean will be improved upon in the future." (from the notes section in the 'ipcclean' utility description: http://www.postgresql.org/docs/8.1/static/app-ipcclean.html) I assume that Postgresql is partly "self-repairing", and will handle any required cleaning when a DRDB slave starts after a DRDB master failure. Best Regards Morten Andersen, Instadia, Denmark