Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 49E28633E4D for ; Thu, 25 Mar 2010 05:12:41 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 56859-03 for ; Thu, 25 Mar 2010 08:12:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by mail.postgresql.org (Postfix) with SMTP id 38915633E5D for ; Thu, 25 Mar 2010 05:11:52 -0300 (ADT) Received: from source ([209.85.219.217]) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKS6saxlweG3mXi/UJXQId2xrpncmoA83W@postini.com; Thu, 25 Mar 2010 01:11:51 PDT Received: by ewy9 with SMTP id 9so1842027ewy.9 for ; Thu, 25 Mar 2010 01:11:49 -0700 (PDT) Received: by 10.213.102.68 with SMTP id f4mr2656926ebo.61.1269504709503; Thu, 25 Mar 2010 01:11:49 -0700 (PDT) Received: from [192.168.1.117] (dsl-hkibrasgw2-ff67c300-165.dhcp.inet.fi [88.195.103.165]) by mx.google.com with ESMTPS id 15sm603190ewy.8.2010.03.25.01.11.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 25 Mar 2010 01:11:48 -0700 (PDT) Message-ID: <4BAB1AC1.7000900@enterprisedb.com> Date: Thu, 25 Mar 2010 10:11:45 +0200 From: Heikki Linnakangas Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706) MIME-Version: 1.0 To: Tom Lane CC: Fujii Masao , Simon Riggs , Aidan Van Dyk , PostgreSQL-development Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL References: <3f0b79eb1002092105r21e009d3v468496058ba04392@mail.gmail.com> <4B743E7D.5070603@enterprisedb.com> <3f0b79eb1002180337t1fab1395ve3491256672af15f@mail.gmail.com> <4BA0B079.3050301@enterprisedb.com> <3f0b79eb1003180727g7877743eq81274e014fe70a49@mail.gmail.com> <1268988724.3556.3.camel@ebony> <4BA361E4.7020309@enterprisedb.com> <3f0b79eb1003230017v16f4ecbeyc20e75beeffe8f1c@mail.gmail.com> <4BAA060A.2020000@enterprisedb.com> <1269472981.8481.8946.camel@ebony> <3f0b79eb1003241908n1e8f38e0q7cd7465163b3d7af@mail.gmail.com> <6198.1269483277@sss.pgh.pa.us> In-Reply-To: <6198.1269483277@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.392 tagged_above=-10 required=5 tests=AWL=0.207, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/999 X-Sequence-Number: 159775 Tom Lane wrote: > Fujii Masao writes: >> OK. How about making the startup process emit WARNING, stop WAL replay and >> wait for the presence of trigger file, when an invalid record is found? >> Which keeps the server up for readonly queries. And if the trigger file is >> found, I think that the startup process should emit a FATAL, i.e., the >> server should exit immediately, to prevent the server from becoming the >> primary in a half-finished state. Also to allow such a halfway failover, >> we should provide fast failover mode as pg_standby does? > > I find it extremely scary to read this sort of blue-sky design > discussion going on now, two months after we were supposedly > feature-frozen for 9.0. We need to be looking for the *rock bottom > minimum* amount of work to do to get 9.0 out the door in a usable > state; not what would be nice to have later on. Agreed, this is getting complicated. I'm already worried about the amount of changes needed to make it work, I don't want to add any new modes. PANIC seems like the appropriate solution for now. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com