Skip to content

Commit 92a5f27

Browse files
Merge pull request #272568 from nachoalonsoportillo/patch-1
Expose all existing pgBouncer server parameters
2 parents cd56cea + b2fcbf9 commit 92a5f27

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

articles/postgresql/flexible-server/concepts-pgbouncer.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: varundhawan
66
ms.service: postgresql
77
ms.subservice: flexible-server
88
ms.topic: conceptual
9-
ms.date: 2/8/2024
9+
ms.date: 4/18/2024
1010
---
1111

1212
# PgBouncer in Azure Database for PostgreSQL - Flexible Server
@@ -32,15 +32,17 @@ You can configure PgBouncer settings by using these parameters.
3232
> [!NOTE]
3333
> 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.
3434
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`). | |
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.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`). | |
4446

4547
For more information about PgBouncer configurations, see the [pgbouncer.ini documentation](https://www.pgbouncer.org/config.html).
4648

0 commit comments

Comments
 (0)