Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 8FD186335DF for ; Thu, 14 May 2009 23:33:02 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 56491-04 for ; Thu, 14 May 2009 23:32:52 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.217.172]) by mail.postgresql.org (Postfix) with ESMTP id 31CB7633285 for ; Thu, 14 May 2009 23:33:01 -0300 (ADT) Received: by gxk20 with SMTP id 20so1078478gxk.19 for ; Thu, 14 May 2009 19:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3CnBrLp4IQ0AkxNWZAYkGXrum28pr6l7HtFPnn8Pa9c=; b=SEe6tgx8r0PMs7D8Y6cRjLd4uV/M94SwXBPSAUmlKsTFJlycmQmt3fBJzeKK0UtddE Vi0rEDDirdXrHr0GJz6RXdux8khhz06r7pAdnM39X4wn/fqNEMuNShS+gNZMtNtRGmOz o0cLzSHKOZaQ6mWx8MypIx5kB6zSOmqhMlDVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tEl3tlVZKgDS9yLwkVUdBj2b3Tb719FYejeKDuNZXcY3OZNwG3VdCBdBmZD0/ov3JF xYqxq+cN/eZ+Z/Td3qINLDeTMEFgOJDoKnaiQaShlAy/xmK6qpVTYUd9E2Yc+0AczGHO PJWJS/ZrjOWlIdV4h4Es2c502VLbHfBndkebI= MIME-Version: 1.0 Received: by 10.151.74.12 with SMTP id b12mr968926ybl.151.1242354779739; Thu, 14 May 2009 19:32:59 -0700 (PDT) In-Reply-To: <4A0C7F96.2040407@enterprisedb.com> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <3f0b79eb0905130127u3a3275b1w79f4d8cb729ded36@mail.gmail.com> <4A0A86D2.9080602@enterprisedb.com> <1985.1242234105@sss.pgh.pa.us> <4A0B10C7.2040309@enterprisedb.com> <1242247404.3843.503.camel@ebony.2ndQuadrant> <1242315415.3843.526.camel@ebony.2ndQuadrant> <3f0b79eb0905141149lf5cef92j538f490c86dfedf8@mail.gmail.com> <1242328204.3843.599.camel@ebony.2ndQuadrant> <4A0C7F96.2040407@enterprisedb.com> Date: Fri, 15 May 2009 11:32:59 +0900 Message-ID: <3f0b79eb0905141932p18409171w365d917fdfe17b82@mail.gmail.com> Subject: Re: New trigger option of pg_standby From: Fujii Masao To: Heikki Linnakangas Cc: Simon Riggs , Tom Lane , Guillaume Smet , Peter Eisentraut , Kevin Grittner , pgsql-hackers Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.285 tagged_above=0 required=5 tests=AWL=0.285 X-Spam-Level: X-Archive-Number: 200905/641 X-Sequence-Number: 138183 Hi, On Fri, May 15, 2009 at 5:31 AM, Heikki Linnakangas wrote: > I've finally committed Simon's recovery_end_command patch, as well as the > changes to pg_standby. There's now smart and fast failover modes, chosen = by > the content of the trigger file, smart mode is the default. A "fast" trig= ger > file is truncated, turning it into a "smart" trigger for subsequent > pg_standby invocations. I believe this is now safe in all the =A0combinat= ions > discussed, in both fast and smart mode, with or without extra WAL files > copied to pg_xlog, and also if the last archived WAL file is incomplete. Thanks for revising my patch and committing it! This seems to work fine in all the case which I described. Regards, --=20 Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center