Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that #847 is merged, when a pool is set to
default_role = replica
(or manually set to replica), and no replicas are available, the primary won't be touched at all. Instead, replicas will be automatically set back to available and will be checked for health again.If you have a single replica and it is actually down, you may find convenient to send queries to the primary until you fix the replica (if the primary can handle the load). To allow this behavior, a new configuration parameter is added to the configuration that will make the
primary
available to receive queries if every replica in the pool is banned.Note that when this is enabled, the replicas won't be automatically
unbanned
(default behavior).