Re: Error promoting slave on cascading replication using replication slots

Alvaro Melo <al_nunes@atua.com.br> wrote:

>
> I found a instruction to add the following line to recovery.conf:
> recovery_target_timeline = 'latest'
>
> When this line is added, slave2 keeps its replication with slave 1:
> 2015-12-17 13:37:54 BRST [868-2] LOG:  replication terminated by primary
> server
> 2015-12-17 13:37:54 BRST [868-3] DETAIL:  End of WAL reached on timeline
> 1 at 0/3001358.
> 2015-12-17 13:37:54 BRST [868-4] LOG:  fetching timeline history file
> for timeline 2 from primary server
> 2015-12-17 13:37:54 BRST [863-7] LOG:  new target timeline is 2
> 2015-12-17 13:37:54 BRST [863-8] LOG:  record with zero length at 0/3001358
> 2015-12-17 13:37:54 BRST [868-5] LOG:  restarted WAL streaming at
> 0/3000000 on timeline 2
>
> My question is: is this the right procedure, or am I missing something?

Yeah, this is the right procedure, afaik.

Slave2 is now in sync with the new timeline, everything is okay.


Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°