Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VpyLf-0004Du-Gu for pgsql-hackers@arkaria.postgresql.org; Mon, 09 Dec 2013 10:45:59 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VpyLe-0005f4-Vl for pgsql-hackers@arkaria.postgresql.org; Mon, 09 Dec 2013 10:45:59 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VpyLd-0005ev-Se for pgsql-hackers@postgresql.org; Mon, 09 Dec 2013 10:45:58 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VpyLa-0004kC-UB for pgsql-hackers@postgresql.org; Mon, 09 Dec 2013 10:45:57 +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 rB9AjkUw026061; Mon, 9 Dec 2013 19:45:46 +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 3C44DE0148; Mon, 9 Dec 2013 19:45:46 +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 30E27E0146; Mon, 9 Dec 2013 19:45:46 +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 rB9Ajk0v011048; Mon, 9 Dec 2013 19:45:46 +0900 Message-ID: <52A5A095.5020002@lab.ntt.co.jp> Date: Mon, 09 Dec 2013 19:51:01 +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: fabriziomello@gmail.com CC: Robert Haas , Simon Riggs , Pgsql Hackers Subject: Re: Time-Delayed Standbys References: <52A59D10.7020209@lab.ntt.co.jp> In-Reply-To: <52A59D10.7020209@lab.ntt.co.jp> Content-Type: text/plain; charset=UTF-8; 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 19:36), KONDO Mitsumasa wrote: > * Problem 1 > I read your wittened document. There is "PITR has not affected". > However, when I run PITR with min_standby_apply_delay=3000000, it cannot start > server. The log is under following. >> [mitsu-ko@localhost postgresql]$ bin/pg_ctl -D data2 start >> server starting >> [mitsu-ko@localhost postgresql]$ LOG: database system was interrupted; last >> known up at 2013-12-08 18:57:00 JST >> LOG: creating missing WAL directory "pg_xlog/archive_status" >> cp: cannot stat `../arc/00000002.history': >> LOG: starting archive recovery >> LOG: restored log file "000000010000000000000041" from archive >> LOG: redo starts at 0/41000028 >> LOG: consistent recovery state reached at 0/410000F0 >> LOG: database system is ready to accept read only connections >> LOG: restored log file "000000010000000000000042" from archive >> FATAL: cannot wait on a latch owned by another process >> LOG: startup process (PID 30501) exited with exit code 1 >> LOG: terminating any other active server processes > We need recovery flag for controling PITR situation. 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. So I think you should add only StandbyModeRequested flag in conditional branch. 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