From: Marko Kreen Date: Thu, 3 Sep 2015 14:17:27 +0000 (+0300) Subject: Update todo X-Git-Tag: pgbouncer_1_7_rc1~9 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6f0af064a44063f7e419947b5fe177ea63cd3647;p=pgbouncer Update todo --- diff --git a/doc/config.rst b/doc/config.rst index 5b15f6a..7167e9c 100644 --- a/doc/config.rst +++ b/doc/config.rst @@ -684,7 +684,10 @@ 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.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 ------------------- diff --git a/doc/todo.rst b/doc/todo.rst index 491b7f9..26a118a 100644 --- a/doc/todo.rst +++ b/doc/todo.rst @@ -8,8 +8,6 @@ Significant amount of users feel the need for those. * Protocol-level plan cache. -* Load-balancing / failover. - * LISTEN/NOTIFY. Requires strict SQL format. Waiting for contributors... @@ -17,6 +15,10 @@ 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 @@ -74,6 +76,10 @@ Problems / cleanups 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.