Update Geo docs to restart PostgreSQL to changes take effect on secondary
What does this MR do?
Update Geo docs to restart PostgreSQL to changes take effect on a Geo secondary node.
Why was this MR needed?
We configure PostgreSQL to listen on network interfaces when enabling the FDW support on a Geo secondary node so we neet to restart it to changes take effect before we initiate the replication process.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
What are the relevant issue numbers?
Edited by Douglas Barbosa Alexandre