Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VqEp6-00069M-DG for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Dec 2013 04:21:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VqEp5-00026U-Sv for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Dec 2013 04:21:27 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VqEp4-00026M-NI for pgsql-hackers@postgresql.org; Tue, 10 Dec 2013 04:21:26 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VqEp2-0006xm-1P for pgsql-hackers@postgresql.org; Tue, 10 Dec 2013 04:21:26 +0000 Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id rBA4LDJg024758; Tue, 10 Dec 2013 13:21:13 +0900 Received: from mfs6.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 02645E0156; Tue, 10 Dec 2013 13:21:13 +0900 (JST) Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id E0F37E0153; Tue, 10 Dec 2013 13:21:12 +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 rBA4LCYv013371; Tue, 10 Dec 2013 13:21:12 +0900 Message-ID: <52A697F3.8030403@lab.ntt.co.jp> Date: Tue, 10 Dec 2013 13:26:27 +0900 From: KONDO Mitsumasa User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Andres Freund CC: fabriziomello@gmail.com, Robert Haas , Simon Riggs , 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> In-Reply-To: <20131209112937.GA27840@awork2.anarazel.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/09 20:29), Andres Freund wrote: > On 2013-12-09 19:51:01 +0900, KONDO Mitsumasa wrote: >> Add my comment. We have to consider three situations. >> >> 1. PITR >> 2. replication standby >> 3. replication standby with restore_command >> >> I think this patch cannot delay in 1 situation. > > Why? I have three reasons. 1. It is written in document. Can we remove it? 2. Name of this feature is "Time-delayed *standbys*", not "Time-delayed *recovery*". Can we change it? 3. I think it is unnessesary in master PITR. And if it can delay in master PITR, it will become master at unexpected timing, not to continue to recovery. It is meaningless. I'd like to ask you what do you expect from this feature and how to use it. 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