Re: replication issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for your response Samed. 

I have set recovery_target_timeline='latest', however getting below error.

2018-04-09 16:58:26 SGT FATAL:  highest timeline 1 of the primary is behind recovery timeline 2
cp: cannot stat ‘/u101/oradata/postgres/standby/pg_xlog/00000003.history’: No such file or directory


On Mon, Apr 9, 2018 at 2:29 PM, Samed YILDIRIM <samed@xxxxxxxxxx> wrote:
Hi Dhandapani,
 
It looks a recover operation or a switchover/failover operation has been applied. You can add following line to your recovery.conf file to follow new timeline.
 
recovery_target_timeline = 'latest'
 
https://www.postgresql.org/docs/10/static/recovery-target-settings.html
https://www.postgresql.org/docs/10/static/continuous-archiving.html#BACKUP-TIMELINES
 
Best regards.


İyi çalışmalar.
Samed YILDIRIM



09.04.2018, 11:52, "Dhandapani Shanmugam" <postgresql95@xxxxxxxxx>:
I am getting below error in logfile

2018-04-09 16:51:00 SGT LOG:  invalid record length at 0/1F000098: wanted 24, got 0
2018-04-09 16:51:00 SGT FATAL:  highest timeline 1 of the primary is behind recovery timeline 2


On Mon, Apr 9, 2018 at 2:11 PM, Dhandapani Shanmugam <postgresql95@xxxxxxxxx> wrote:
Hi All,

I am setting up streaming replication and getting below error when starting the postgreSQL instance on stanby server. Need your expert advise

postgres 26110 26108  0 16:35 ?        00:00:00 postgres: startup process   recovering 00000002000000000000001F

Below are my content of recovery.conf

standby_mode = 'on'
primary_conninfo = 'host=188.33.44.33 port=5432 user=replication'
restore_command = 'cp /u101/oradata/postgres/standby/pg_xlog/%f  %p'

-D



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux