Re: WAL replay asking for very old WAL

I guess the only issue I have existed between the keyboard and chair. Thanks for your time and patients.

Stephen Kuntz | Systems Administrator
Pelmorex Media Inc.
T: 905.829.1159 x1376

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of MirrorX
Sent: Monday, March 7, 2016 12:01 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] WAL replay asking for very old WAL

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(at)postgresql(dot)org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin