-
Notifications
You must be signed in to change notification settings - Fork 572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't restart the cluster, when a reload will suffice #291
Labels
Comments
This was referenced Apr 3, 2018
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If any config change is made, then the cluster is "restarted". This will cause downtime and disconnect all sessions.
Many config changes can be implemented with a "reload", which simply re-reads the
postgresql.conf
.The text was updated successfully, but these errors were encountered: