config.txt: hint that all timeouts can be specified as floats

During discussion with Keyur Govande we found out that all timeouts
can be specified as float since 1.4, except reserve_pool_timeout,
which works since 1.5.2.

Add a hints to documentation about that.

diff --git a/doc/config.txt b/doc/config.txt
index 1709bab82565443874d41637b38c9a4fd523359f..52fa3d214626e590d60c0d91c5c0e13c2d826081 100644 (file)
--- a/doc/config.txt
+++ b/doc/config.txt
@@ -177,7 +177,7 @@ Default: 0 (disabled)
 If a client has not been serviced in this many seconds, pgbouncer enables
 use of additional connections from reserve pool.  0 disables.
 
-Default: 5
+Default: 5.0
 
 ==== server_round_robin ====
 
@@ -298,7 +298,7 @@ Default: DISCARD ALL
 How long to keep released connections available for immediate re-use, without running
 sanity-check queries on it. If 0 then the query is ran always.
 
-Default: 30
+Default: 30.0
 
 ==== server_check_query ====
 
@@ -314,7 +314,7 @@ The pooler will try to close server connections that have been connected longer
 than this. Setting it to 0 means the connection is to be used only once,
 then closed. [seconds]
 
-Default: 3600
+Default: 3600.0
 
 ==== server_idle_timeout ====
 
@@ -322,21 +322,21 @@ If a server connection has been idle more than this many seconds, and there are
 too many connections in the pool, this one can be dropped.
 If 0 then timeout is disabled.  [seconds]
 
-Default: 600
+Default: 600.0
 
 ==== server_connect_timeout ====
 
 If connection and login won't finish in this amount of time, the connection 
 will be closed. [seconds]
 
-Default: 15
+Default: 15.0
 
 ==== server_login_retry ====
 
 If login failed, because of failure from connect() or authentication that
 pooler waits this much before retrying to connect. [seconds]
 
-Default: 15
+Default: 15.0
 
 ==== client_login_timeout ====
 
@@ -344,7 +344,7 @@ If a client connects but does not manage to login in this amount of time, it
 will be disconnected. Mainly needed to avoid dead connections stalling 
 SUSPEND and thus online restart. [seconds]
 
-Default: 60
+Default: 60.0
 
 ==== autodb_idle_timeout ====
 
@@ -352,7 +352,7 @@ If the automatically created (via "*") database pools have
 been unused this many seconds, they are freed.  The negative
 aspect of that is that their statistics are also forgotten.  [seconds]
 
-Default: 3600
+Default: 3600.0
 
 ==== dns_max_ttl ====
 
@@ -360,7 +360,7 @@ How long the DNS lookups can be cached.  If a DNS lookup returns
 several answers, pgbouncer will robin-between them in the meantime.
 Actual DNS TTL is ignored.  [seconds]
 
-Default: 15
+Default: 15.0
 
 ==== dns_zone_check_period ====
 
@@ -374,7 +374,7 @@ are invalidated.
 
 Works only with UDNS backend (`--with-udns` to configure).
 
-Default: 0 (disabled)
+Default: 0.0 (disabled)
 
 === Dangerous timeouts ===
 
@@ -386,7 +386,7 @@ Queries running longer than that are canceled. This should be used only with
 slightly smaller server-side statement_timeout, to apply only for network
 problems. [seconds]
 
-Default: 0 (disabled)
+Default: 0.0 (disabled)
 
 ==== query_wait_timeout ====
 
@@ -394,7 +394,7 @@ Maximum time queries are allowed to spend waiting for execution. If the query
 is not assigned to a server during that time, the client is disconnected. This
 is used to prevent unresponsive servers from grabbing up connections. [seconds]
 
-Default: 0 (disabled)
+Default: 0.0 (disabled)
 
 ==== client_idle_timeout ====
 
@@ -402,14 +402,14 @@ Client connections idling longer than this many seconds are closed. This should
 be larger than the client-side connection lifetime settings, and only used 
 for network problems. [seconds]
 
-Default: 0 (disabled)
+Default: 0.0 (disabled)
 
 ==== idle_transaction_timeout ====
 
 If client has been in "idle in transaction" state longer,
 it will be disconnected.  [seconds]
 
-Default: 0 (disabled)
+Default: 0.0 (disabled)
 
 === Low-level network settings ===