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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
