On Fri, May 8, 2015 at 2:29 PM James Sewell
wrote:
> Hello All,
>
> I am running 9.4 on Centos.
>
> I have three servers, one master and two slaves. The slaves have the
> following recovery.conf
>
> standby_mode = 'on'
> primary_conninfo = 'user=postgres host=mastervip port=5432'
> restore_comman
OK I think I have a solution, using the following script as the
restore_command
echo $1 | grep history > /dev/null
if [ $? -eq 0 ]; then
exit 1
fi
scp postgres@postgres3:/archived_wals/$1 $2
This seems to work, as it restricts slave servers from switching timeline
from the archive by
Hey,
This is an example of what I see when starting up a replica and attaching
it to a master.
In this case the master is in timeline 3, but the archive log goes up to
timeline 6.
2015-05-08 16:23:07 AEST @ ( 0 0)LOG: database system was interrupted;
last known up at 2015-05-08 16:21:14 AES
