Re: Recovery - New Slave PostgreSQL 9.2

* NOTE: I ran the pg_basebackup from another STANDBY SERVER. Not from the MASTER

Lucas Possamai

kinghost.co.nz

On 9 January 2016 at 15:28, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:

Still trying to solve the problem...

Anyone can help please?

Lucas

Lucas Possamai

kinghost.co.nz

On 9 January 2016 at 14:45, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:

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

On 9 January 2016 at 14:37, Ian Barwick <ian@2ndquadrant.com> wrote:

On 16/01/09 9:23, drum.lucas@gmail.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