Skip auto-restart of PG during reconfigure as part of pg-upgrade
What does this MR do?
In nodes where Geo PG runs along with regular PG, during the PG upgrade
process of regular PG, a reconfigure is initiated. This reconfigure will
update the VERSION
file in Geo PG's directory also with the new
verison information and trigger a restart of the Geo PG. However,
because Geo PG's data is still of the old version but the binaries have
already been updated to point to the new version, this restart will fail
due to mismatch.
Because PG upgrade anyways causes the DB to be stopped and started, we can safely skip the automatic restart as part of reconfigure and avoid this failure.
Related issues
Closes #6856 (closed)
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