Re: Recovery - New Slave PostgreSQL 9.2

Sure... Here's the total information:
http://superuser.com/questions/1023770/new-postgresql-slave-server-error-timeline

recovery.conf:

restore_command = 'exec nice -n 19 ionice -c 2 -n 7
../../bin/restore_wal_segment.bash "../wal_archive/%f" "%p"'
archive_cleanup_command = 'exec nice -n 19 ionice -c 2 -n 7
../../bin/pg_archivecleaup_mv.bash -d "../wal_archive" "%r"'
recovery_target_timeline = 'latest'
standby_mode = on
primary_conninfo = 'host=192.168.100.XX port=5432 user=replicator
application_name=replication_new_slave'

Lucas Possamai

kinghost.co.nz
<http://forum.kinghost.co.nz/memberlist.php?mode=viewprofile&u=2&sid=e999f8370385657a65d41d5ff60b0b38>

On 9 January 2016 at 14:37, Ian Barwick <ian(at)2ndquadrant(dot)com> wrote:

> On 16/01/09 9:23, drum(dot)lucas(at)gmail(dot)com wrote:
> > Hi all!
> >
> > I've done the pg_basebackup from the live to a new slave server...
> >
> > I've recovery the wal files, but now that I configured to replicate from
> the master (recovery.conf) I got this error:
> >
> > ../wal_archive/0000000400000C68000000C8` not found
> > ../wal_archive/00000005.history` not found
> >
> > FATAL: timeline 2 of the primary does not match recovery target
> timeline 1
>
> Can you post the contents of your recovery.conf file, suitably
> anonymised if necessary?
>
> Regards
>
> Ian Barwick
>
> --
> Ian Barwick http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
>