2017-01-06 13:09 GMT+01:00 Michael Paquier <michael.paquier@xxxxxxxxx>:
Hi,On Fri, Jan 6, 2017 at 1:01 AM, Tom DalPozzo <t.dalpozzo@xxxxxxxxx> wrote:
> Hi,
> there is something happening in my replication that is not clear to me. I
> think I'm missing something.
> I've two server, red and blue.
> red is primary blue is standby, async repl.
> Now:
> 1 cleanly stop red
> 2 promote blue
> 3 insert tuples in blue
> 4 from red site, pg_rewind from blue to red dir.
> 5 start red as standby-> OK
> 6 wait a long time and then cleanly stop blue
> 7 promote red
> 8 insert tuples in red
> 9 from blue site, pg_rewind from red to blue dir
> 10 start blue as standby -> I get "requested timeline 3 doesn't contain
> minimum recovery point 1/... on timeline 1
>
> Sometimes this "switching game" works up to timeline 4 or 5, not always 3
Could you give more details? What does pg_rewind tell you at each
phase? Is that on Postgres 9.5 or 9.6? I use pg_rewind quite
extensively on 9.5 but I have no problems of this time with multiple
timeline jumps when juggling between two nodes. Another thing that is
coming to my mind: you are using pg_rewing with a source node that is
running. You should issue a checkpoint manually after promoting the
node to be sure that its control file gets the new timeline number.
--
Michael
sometimes pg_rewind says that nothing needs to be done, sometimes it says it's rewinding and done at the end.
I'm using 9.6. I moved there from 9.5 as I'm also using replication slots and in 9.6 there is a second parameter added. But I seem to remember that it did the same in 9.5 too but I'm not really sure.
I checked that the server, at promotion said the message about the new timeline.
I will make some more tests.
Regards
Pupillo
