doc: Document reconnect behavior on reload and DNS change

This is long-standing behavior, just make the documentation about it
more explicit.

diff --git a/doc/config.rst b/doc/config.rst
index 9f898df4dc06622f40dfd55d113ecafd36f56931..c6064db240370232967bb7004eb963df8c38b2b8 100644 (file)
--- a/doc/config.rst
+++ b/doc/config.rst
@@ -848,7 +848,10 @@ host
 ----
 
 Host name or IP address to connect to.  Host names are resolved
-on connect time, the result is cached per ``dns_max_ttl`` parameter.
+at connect time, the result is cached per ``dns_max_ttl`` parameter.
+When a host name's resolution changes, existing server connections are
+automatically closed when they are released (according to the pooling
+mode), and new server connections immediately use the new resolution.
 If DNS returns several results, they are used in round-robin
 manner.
 

diff --git a/doc/usage.rst b/doc/usage.rst
index b2018422e9d836c5d3c5f8a98d6d1a486c421a4d..a41197f9edda57f965f03b5e7ba667ff1fd8944c 100644 (file)
--- a/doc/usage.rst
+++ b/doc/usage.rst
@@ -613,6 +613,13 @@ RELOAD;
 The PgBouncer process will reload its configuration file and update
 changeable settings.
 
+PgBouncer notices when a configuration file reload changes the
+connection parameters of a database definition.  An existing server
+connection to the old destination will be closed when the server
+connection is next released (according to the pooling mode), and new
+server connections will immediately use the updated connection
+parameters.
+
 Other commands
 ~~~~~~~~~~~~~~