We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In many cases the primary and a secondary must keep the same configuration, in case of a switchover.
In many cases people forget to propagate these changes. So a promoted primary will not archive, its work_mem will be different...
A new service could compare the pg_settings of a primary and a slave and raise a warning if there is a difference.
Optional --exclude option for some parameters that may differ (like cluster_name on Debian)
The text was updated successfully, but these errors were encountered:
Just wondering if this service should include pg_hba_file_rules (10+) or if it should be another service. IMHO, the latter.
Sorry, something went wrong.
I forgot this and complained again in #283 , with more details, so I close this one.
No branches or pull requests
In many cases the primary and a secondary must keep the same configuration, in case of a switchover.
In many cases people forget to propagate these changes. So a promoted primary will not archive, its work_mem will be different...
A new service could compare the pg_settings of a primary and a slave and raise a warning if there is a difference.
Optional --exclude option for some parameters that may differ (like cluster_name on Debian)
The text was updated successfully, but these errors were encountered: