Alexander KukushkinandGitHub 37c1552c0a Smart pg_rewind (#417) ...

Previously we were running pg_rewind only in limited amount of cases:
 * when we knew postgres was a master (no recovery.conf in data dir)
 * when we were doing a manual switchover to a specific node (no
   guaranty that this node is the most up-to-date)
 * when a given node has nofailover tag (it could be ahead of new master)

This approach was kind of working in most of the cases, but sometimes we
were executing pg_rewind when it was not necessary and in some other
cases we were not executing it although it was needed.

The main idea of this PR is first try to figure out that we really need
to run pg_rewind by analyzing timelineid, LSN and history file on master
and replica and run it only if it's needed.

2017-05-19 16:32:06 +02:00

..

steps

AT for master_start_timeout + minor fixes (#361)

2016-12-09 12:02:41 +01:00

basic_replication.feature

Smart pg_rewind (#417)

2017-05-19 16:32:06 +02:00

cascading_replication.feature

Add synchronous replication support. (#314)

2016-10-19 16:12:51 +02:00

environment.py

Smart pg_rewind (#417)

2017-05-19 16:32:06 +02:00

patroni_api.feature

Scheduled failovers in 1 second don't work reliably with loop_wait=2

2017-01-13 11:25:07 +01:00