Thread: Help on recovering my standby
Hi I have my standby (streaming replication) down due to missing wal files. You would see the same error in the logs stating “cannot find the wal file …”
What is the best way to get it going so that when we switch between standby and primary once in a while they are in sync?
Currently I am working on a CERT server and hence there is no outage concerns. I need to repeat the same process on prod once I get it going successfully. Any help is appreciated.
Thanks
Kumar Ramalingam
Global Database Administration
Elavon, Atlanta , GA
678 731 5288
The information contained in this e-mail and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. This message has been scanned for known computer viruses.
On Tuesday 21 June 2016 19:34:18 Ramalingam, Sankarakumar wrote: > Hi I have my standby (streaming replication) down due to missing wal files. > You would see the same error in the logs stating "cannot find the wal file > ..." What is the best way to get it going so that when we switch between > standby and primary once in a while they are in sync? > > Currently I am working on a CERT server and hence there is no outage > concerns. I need to repeat the same process on prod once I get it going > successfully. Any help is appreciated. > You should keep your WAL files from the master for at least as long as the slave might be offline (plus startup time), somewhere the slave can copy them from when needed (shared file system, object store, scp target, whatever). See the postgresql.conf parameter archive_command and the corresponding recovery.conf parameter restore_command.
On Tuesday 21 June 2016 19:34:18 Ramalingam, Sankarakumar wrote:
> Hi I have my standby (streaming replication) down due to missing wal files.
> You would see the same error in the logs stating "cannot find the wal file
> ..." What is the best way to get it going so that when we switch between
> standby and primary once in a while they are in sync?
>
> Currently I am working on a CERT server and hence there is no outage
> concerns. I need to repeat the same process on prod once I get it going
> successfully. Any help is appreciated.
>
You should keep your WAL files from the master for at least as long as the
slave might be offline (plus startup time), somewhere the slave can copy them
from when needed (shared file system, object store, scp target, whatever).
See the postgresql.conf parameter archive_command and the corresponding
recovery.conf parameter restore_command.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
If you are truly missing WAL files in your slave/standy, then you need to rebuild the slave as per standard procedures.
SELECT pg_reload_conf();
--
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
![](http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif)