I think there is no need to define restore_command in recovery.conf file if you are already creating a replication slot. please correct me if I am wrong as far as I know restore_command is needed when you are archiving xlog file to archive location but if you have replication slot then there is no need of restore_command . please correct me If I am wrong ?
Hi, Thanks for your tutorial.. Can we do switchover and switchback without adding parameter recovery _target_timeline='latest' in 9.4 My friend told me he has done switchover and switchback in 9.5 without adding recovery _target_timeline=latest. is it possible ?
Everything works great until I remove the replication slot. I immediately get replication terminated by primary server. Only a pg_basebackup gets me out of it.
I did not add recovery_target_timeline = 'latest' to the recovery.conf on the replica which caused all kinds of funkiness; WAL streaming at LOG: replication terminated by primary server DETAIL: End of WAL reached on timeline. DOH!
Hi! Do i need Replication slots for this situation (failback) or i can do it without slots? Thanks
I think there is no need to define restore_command in recovery.conf file if you are already creating a replication slot. please correct me if I am wrong as far as I know restore_command is needed when you are archiving xlog file to archive location but if you have replication slot then there is no need of restore_command . please correct me If I am wrong ?
Hi,
Thanks for your tutorial..
Can we do switchover and switchback without adding parameter recovery _target_timeline='latest' in 9.4
My friend told me he has done switchover and switchback in 9.5 without adding recovery _target_timeline=latest. is it possible ?
Nice! I can't wait to try this.
Hello. Its not working v12 do you have any solution about it
Version 12 doesn't use recovery.conf but recovery.signal, standby.signal and postgresql.auto.conf.
Everything works great until I remove the replication slot. I immediately get replication terminated by primary server. Only a pg_basebackup gets me out of it.
I did not add recovery_target_timeline = 'latest' to the recovery.conf on the replica which caused all kinds of funkiness; WAL streaming at LOG: replication terminated by primary server DETAIL: End of WAL reached on timeline. DOH!