Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr1P7-0004ar-KV for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Dec 2013 08:13:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Vr1P6-0003kF-VF for pgsql-hackers@arkaria.postgresql.org; Thu, 12 Dec 2013 08:13:53 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr1P5-0003k6-F9 for pgsql-hackers@postgresql.org; Thu, 12 Dec 2013 08:13:51 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Vr1P1-0002z0-Ll for pgsql-hackers@postgresql.org; Thu, 12 Dec 2013 08:13:50 +0000 Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id rBC8Dbuf013042; Thu, 12 Dec 2013 17:13:37 +0900 Received: from mfs5.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 2AEEEE0153; Thu, 12 Dec 2013 17:13:37 +0900 (JST) Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 154D4E0152; Thu, 12 Dec 2013 17:13:37 +0900 (JST) Received: from [129.60.241.67] ([129.60.241.67]) by imail3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id rBC8DaKC011929; Thu, 12 Dec 2013 17:13:37 +0900 Message-ID: <52A97189.2040009@lab.ntt.co.jp> Date: Thu, 12 Dec 2013 17:19:21 +0900 From: KONDO Mitsumasa User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: fabriziomello@gmail.com, Andres Freund CC: Simon Riggs , Robert Haas , Pgsql Hackers Subject: Re: Time-Delayed Standbys References: <52A59D10.7020209@lab.ntt.co.jp> <52A5A095.5020002@lab.ntt.co.jp> <20131209112937.GA27840@awork2.anarazel.de> <52A697F3.8030403@lab.ntt.co.jp> <20131210093848.GG27840@awork2.anarazel.de> <52A807F5.4020203@lab.ntt.co.jp> <20131211214712.GA536@awork2.anarazel.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-TM-AS-MML: No X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org (2013/12/12 7:23), Fabrízio de Royes Mello wrote: > On Wed, Dec 11, 2013 at 7:47 PM, Andres Freund > * hot_standby=off: Makes delay useable with wal_level=archive (and thus > > a lower WAL volume) > > * standby_mode=off: Configurations that use tools like pg_standby and > > similar simply don't need standby_mode=on. If you want to trigger > > failover from within the restore_command you *cannot* set it. > > * recovery_target_*: It can still make sense if you use > > pause_at_recovery_target. I don't think part of his arguments are right very much... We can just set stanby_mode=on when we use "min_standby_apply_delay" with pg_standby and similar simply tools. However, I tend to agree with not to need to prohibit except for standby_mode. So I'd like to propose that changing parameter name of "min_standby_apply_delay" to "min_recovery_apply_delay". It is natural for this feature. Regards, -- Mitsumasa KONDO NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers