Veeam Backup for Microsoft 365 • Re: Pgbouncer vs npgsql connection pool

We have implemented pgBouncer primarily to reduce the computational overhead associated with establishing new PostgreSQL connections and to limit the number of backend connections. This approach is especially beneficial for workloads characterized by frequent, short-lived connections, as you observed.
The confusion regarding the use of both “maximum pool size” and “maxpoolsize” parameters in connection strings should be addressed in the next product update.

On the simultaneous use of both Npgsql’s built-in pooling and pgBouncer, our plan is to consolidate connection management on one side—most likely relying on pgBouncer for pooling. There're also some longer-term plans on improving our cache databases.

We appreciate your insights and suggestions. Your feedback has been shared with our development team for further consideration.

Statistics: Posted by Polina — Oct 01, 2025 2:30 pm