Document restart vs reload of PostgreSQL during reconfigure
What does this MR do?
One of the remedies mentioned in #2526 regarding omnibus, postgres, and postgres configuration changes was to document that omnibus only reloads postgres during a reconfigure, leaving postgres restarts to be run manually by administrators. This MR describes the situation and gives the user two methods of determining which settings will require a postgres restart as opposed to a simple reconfigure.
Writing this as a result of a customer interaction in this internal zendesk ticket
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
Edited by Diana Stanley