Re: requested timeline ... does not contain minimum recovery point ...

> On Jul 12, 2018, at 19:22, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>> On Jul 12, 2018, at 17:52, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>> Wild guess: you did not issue a checkpoint on the promoted standby
>> before running pg_rewind.
>
> I don't believe a manual checkpoint was done on the target (promoted standby, new master), but it did one as usual during startup after the timeline switch:
>
>> 2018-07-10 19:28:38 UTC [5068]: [1-1] user=,db=,app=,client= LOG: checkpoint starting: force
>
> The pg_rewind was started about 90 seconds later.

That being said, the pg_rewind output seems to indicate that the old divergence point was still being picked up, rather than the one on timeline 104:

> servers diverged at WAL position A58/50000000 on timeline 103
> rewinding from last common checkpoint at A58/4E0689F0 on timeline 103

--
-- Christophe Pettus
xof(at)thebuild(dot)com