Always `pg_rewind` when Patroni primary resumes
What does this MR do?
Based on results from testing in &2588 (comment 459971193) - always set pg_rewind
to true.
Worst case - we'll get an error on the cluster and a database administrator will need to clean up the aftermath - which is no different than the current failure states.
Related issues
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion
Required
-
Merge Request Title, and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks -
trigger-package
has a green pipeline running against latest commit
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for the GitLab Chart opened
Related &2588 (comment 459971193)
Related #5759 (closed)
Related #5746 (closed)
Edited by DJ Mountney