Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1acyX4-0002e1-5e for pgsql-admin@arkaria.postgresql.org; Mon, 07 Mar 2016 17:01:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1acyX3-00005r-FG for pgsql-admin@arkaria.postgresql.org; Mon, 07 Mar 2016 17:01:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1acyX3-00005j-1J for pgsql-admin@postgresql.org; Mon, 07 Mar 2016 17:01:21 +0000 Received: from mbob.nabble.com ([162.253.133.15]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1acyWv-0001xJ-P5 for pgsql-admin@postgresql.org; Mon, 07 Mar 2016 17:01:20 +0000 Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 61DB22260401 for ; Mon, 7 Mar 2016 08:52:27 -0800 (PST) Date: Mon, 7 Mar 2016 10:01:11 -0700 (MST) From: MirrorX To: pgsql-admin@postgresql.org Message-ID: <1457370071685-5891083.post@n5.nabble.com> In-Reply-To: References: <1457365703223-5891066.post@n5.nabble.com> <1457367156570-5891074.post@n5.nabble.com> Subject: Re: WAL replay asking for very old WAL MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.3 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org this message -> -- 2016-03-07 16:04:56 UTC LOG: started streaming WAL from primary at 581D/84000000 on timeline 1 -- that the server has connected to the master via streaming replication so it should get the new xlogs without restarting. you can check that this is happening if you check the pg_last_xlog_receive_location() and pg_last_xlog_replay_location(). if the only problem is that the database is not online in read-only mode, then maybe the only thing missing is to enable the 'hot_standby = on' in the postgresql.conf -- View this message in context: http://postgresql.nabble.com/WAL-replay-asking-for-very-old-WAL-tp5891050p5891083.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin