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
Copy file name to clipboardExpand all lines: articles/postgresql/flexible-server/concepts-pgbouncer.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: varundhawan
6
6
ms.service: postgresql
7
7
ms.subservice: flexible-server
8
8
ms.topic: conceptual
9
-
ms.date: 2/8/2024
9
+
ms.date: 4/18/2024
10
10
---
11
11
12
12
# PgBouncer in Azure Database for PostgreSQL - Flexible Server
@@ -32,15 +32,17 @@ You can configure PgBouncer settings by using these parameters.
32
32
> [!NOTE]
33
33
> The following list of PgBouncer server parameters is visible on the **Server parameters** pane only if the `pgbouncer.enabled` server parameter is set to `true`. Otherwise, they're deliberately hidden.
34
34
35
-
| Parameter name | Description | Default |
36
-
|----------------------|--------|-------------|
37
-
|`pgbouncer.default_pool_size`| Set this parameter value to the number of connections per user/database pair. |`50`|
38
-
|`pgbouncer.max_client_conn`| Set this parameter value to the highest number of client connections to PgBouncer that you want to support. |`5000`|
39
-
|`pgbouncer.pool_mode`| Set this parameter value to `TRANSACTION` for transaction pooling (which is the recommended setting for most workloads). |`TRANSACTION`|
40
-
|`pgbouncer.min_pool_size`| Add more server connections to the pool if the number is below this minimum. |`0` (disabled) |
41
-
|`pgbouncer.ignore_startup_parameters`| Enter a comma-separated list of parameters that PgBouncer can ignore. For example, you can let PgBouncer ignore the `extra_float_digits` parameter. Some parameters are allowed; all others raise an error. This ability is needed to tolerate overenthusiastic Java Database Connectivity (JDBC) wanting to unconditionally set `extra_float_digits=2` in startup packets. Use this option if the library that you use reports errors such as `pq: unsupported startup parameter: extra_float_digits`. ||
42
-
|`pgbouncer.query_wait_timeout`| Set the maximum time (in seconds) that queries are allowed to spend waiting for execution. If the query isn't assigned to a server during that time, the client is disconnected. |`120s`|
43
-
|`pgbouncer.stats_users`| Optional. Set this parameter value to the name of an existing user, to be able to log in to the special PgBouncer statistics database (named `PgBouncer`). ||
|`pgbouncer.default_pool_size`| Set this parameter value to the number of connections per user/database pair. |`50`|
38
+
|`pgbouncer.ignore_startup_parameters`| Enter a comma-separated list of parameters that PgBouncer can ignore. For example, you can let PgBouncer ignore the `extra_float_digits` parameter. Some parameters are allowed; all others raise an error. This ability is needed to tolerate overenthusiastic Java Database Connectivity (JDBC) wanting to unconditionally set `extra_float_digits=2` in startup packets. Use this option if the library that you use reports errors such as `pq: unsupported startup parameter: extra_float_digits`. ||
39
+
|`pgbouncer.max_client_conn`| Set this parameter value to the highest number of client connections to PgBouncer that you want to support. |`5000`|
40
+
|`pgbouncer.max_prepared_statements`| When this is set to a non-zero value PgBouncer tracks protocol-level named prepared statements related commands sent by the client in transaction and statement pooling mode. |`0`|
41
+
|`pgbouncer.min_pool_size`| Add more server connections to the pool if the number is below this minimum. |`0` (disabled) |
42
+
|`pgbouncer.pool_mode`| Set this parameter value to `TRANSACTION` for transaction pooling (which is the recommended setting for most workloads). |`TRANSACTION`|
43
+
|`pgbouncer.query_wait_timeout`| Set the maximum time (in seconds) that queries are allowed to spend waiting for execution. If the query isn't assigned to a server during that time, the client is disconnected. |`120s`|
44
+
|`pgbouncer.server_idle_timeout`| Comma-separated list of database users that are allowed to connect and run read-only queries on the pgBouncer console. |`600s`|
45
+
|`pgbouncer.stats_users`| Optional. Set this parameter value to the name of an existing user, to be able to log in to the special PgBouncer statistics database (named `PgBouncer`). ||
44
46
45
47
For more information about PgBouncer configurations, see the [pgbouncer.ini documentation](https://www.pgbouncer.org/config.html).
0 commit comments