Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 60D7E63299E for ; Wed, 25 Mar 2009 06:32:29 -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 96217-10 for ; Wed, 25 Mar 2009 06:32:22 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mail.postgresql.org (Postfix) with ESMTP id A754A63381E for ; Wed, 25 Mar 2009 06:32:14 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id l9so3060232rvb.43 for ; Wed, 25 Mar 2009 02:32:12 -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=Fpx4Sp8yrHRrxb4WvvnJ8VJRzmznoC3uVWKc2hmJp0o=; b=ST4GGv9hOPHTSqTTwH6FXAjQ98OZKePP+qiIhhbYk1w2bGyF+I7arD7yGmFndZn8c+ //cyDvXVaMaNYKbNu1NZTktMp0C7v6+8US72gPKU8OdYI7jV6lKezBhRSCtP6aXYSmWQ T1uR5yDaL1+IJbhbzb3E5vX4WCdF1QGB/+/+8= 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=yEOjBA9RFn9sPDg5D4YkK0sKRUJJXdEuoWTl3g5zUAzB3bnvgyoT76vb+oUpWoV7Ph uZgH85GCHhkcTPaIWKP5eENxIwk+liX8Jl4+NDil2o6SPVCVP28G/Rmeoc1Nyx40s89a gtZ340T8xyZpmFNWhrztBeuP8B7bhSwesLNyY= MIME-Version: 1.0 Received: by 10.140.174.11 with SMTP id w11mr3478609rve.83.1237973532486; Wed, 25 Mar 2009 02:32:12 -0700 (PDT) In-Reply-To: <1d4e0c10903250155w34bd79dcvfab2ad5c95e56011@mail.gmail.com> References: <3f0b79eb0903242329j12865d55s348f5c873a956e71@mail.gmail.com> <1d4e0c10903242350i505a9f6bsa7ba347dc02f90b6@mail.gmail.com> <3f0b79eb0903250144k453b3927mffa8b08678ed057b@mail.gmail.com> <1d4e0c10903250155w34bd79dcvfab2ad5c95e56011@mail.gmail.com> Date: Wed, 25 Mar 2009 18:32:12 +0900 Message-ID: <3f0b79eb0903250232y34c06a77jafdc17a45d1e9d1f@mail.gmail.com> Subject: Re: New trigger option of pg_standby From: Fujii Masao To: guillaume.smet@gmail.com Cc: pgsql-hackers 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=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/976 X-Sequence-Number: 135654 Hi, On Wed, Mar 25, 2009 at 5:55 PM, Guillaume Smet wrote: > On Wed, Mar 25, 2009 at 9:44 AM, Fujii Masao wrote: >> Yeah, I agree... but there may be scripts for warm-standby based on >> the existing default behavior. So, I didn't make a new trigger the default. > > I don't use pg_standby personnaly but I admit I'm quite surprised by > the current behaviour. I'm pretty sure a lot of the current users > would be surprised too. The current behavior is documented as follows, so it may be taken for granted by some users. I think that we shouldn't ignore such users. --------------- Specify a trigger file whose presence should cause recovery to end whether or not the next WAL file is available. --------------- Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center