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.0 (disabled)
+It also helps when server is down or database rejects connections for any reason.
+If this is disabled, clients will be queued infinitely.
+
+Default: 120
client_idle_timeout
-------------------
* Protocol-level plan cache.
-* Load-balancing / failover.
-
* LISTEN/NOTIFY. Requires strict SQL format.
Waiting for contributors...
Conceptual issues
-----------------
+* Bad naming in data strctures:
+ * PgSocket->auth_user [vs. PgDatabase->auth_user]
+ * PgSocket->db [vs. PgPool->db]
+
* **server_reset_query** vs. per-db **pool_mode**. Session and transaction
pooling mode should not use same **server_reset_query**.
For session-pooling it should be ``DISCARD ALL``, for non-session pooling
Dubious/complicated features
----------------------------
+* Load-balancing / failover. Both are already solved via DNS.
+ Adding load-balancing config in pgbouncer might be good idea.
+ Adding failover decision-making is not...
+
* User-based route. Simplest would be to move db info to pool
and fill username into dns.