Files
patroni/tests
Alexander KukushkinandGitHub 80fbe90056 Issue CHEKPOINT explicitely after promote happened (#1498)
It is safe to call pg_rewind on the replica only when pg_control on the primary contains information about the latest timeline. Postgres is usually doing immediate checkpoint right after promote and in most cases it works just fine. Unfortunately we regularly receive complaints that it takes to long (minutes) until the checkpoint is done and replicas can't perform rewind. At the same time doing the checkpoint manually immediately helped. So Patroni starts doing the same. When the promotion happened and postgres is not running in recovery, we explicitly issue the checkpoint.

We are intentionally not using the AsyncExecutor here, because we want the HA loop continues doing its normal flow.
2020-04-20 11:55:05 +02:00
..
2019-12-04 11:28:46 +01:00
2019-08-05 15:08:04 +02:00
2020-04-09 10:34:35 +02:00
2019-12-04 11:28:46 +01:00
2020-04-09 10:34:35 +02:00
2020-04-15 12:18:49 +02:00
2020-04-15 12:18:49 +02:00
2020-04-09 10:34:35 +02:00