The PgBouncer configuration is not described in the documentation

Hello,

Currently the documentation does not mention pgbouncer in any way even though it is recommended in a production environment with a PostgresSQL database. It would be great if we could describe why we need PGBouncer, the recommended configuration, and ways to tunning this component.

For inspiration, we can read the Heroku documentation: https://devcenter.heroku.com/articles/best-practices-pgbouncer-configuration

Best regards, Kamil Breguła

[alexmc-ms]

Pgbouncer is critical for cloud setups using Azure Database for Postgresql. For almost a year, my team was using 1.10.9 in a Production environment running Azure Sql Server. In order to upgrade to 1.10.14, we needed to move to Postgresql as support for Sql Server has degraded to unusable at this point. The default connection pooling to Azure Sql Server worked fine. The default connection pooling to Azure Database for Postgresql was terrible resulting in a 16 CPU database using 85% CPU at all times. We added pgbouncer and CPU usage immediately dropped to 1%.

Steps for setting this up in Azure are here: https://techcommunity.microsoft.com/t5/azure-database-for-postgresql/steps-to-install-and-setup-pgbouncer-connection-pooling-proxy/ba-p/730555.

[eladkal]

I believe this is covered by https://github.com/apache/airflow/pull/18399