You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a host is resolved, pgbouncer checks all server connections for this host and tags connections using IPs not found in the new resolved list as dirty (close_needed). It would be helpful to be able to disable this behavior. This would help avoiding connection churn in scenarios where, for example, the host might return a list of different IP addresses every time (think weighted routing in Route53).
Another option to help with these scenarios would be to provide an admin command like RELOAD_DNS which would force host resolution regardless of the host's DNS TTL (dns_max_ttl).
What
Currently, when a host is resolved, pgbouncer checks all server connections for this host and tags connections using IPs not found in the new resolved list as dirty (
close_needed
). It would be helpful to be able to disable this behavior. This would help avoiding connection churn in scenarios where, for example, the host might return a list of different IP addresses every time (think weighted routing in Route53).Another option to help with these scenarios would be to provide an admin command like
RELOAD_DNS
which would force host resolution regardless of the host's DNS TTL (dns_max_ttl
).How
Options:
The text was updated successfully, but these errors were encountered: