Re: pgbouncer best practices

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: Rita <rmorgan466(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pgbouncer best practices
Date: 2023-07-08 13:46:37
Message-ID: f3d5bc21-205e-78ff-d952-7b980cd861b7@silentmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Rita wrote on 7/8/23 4:27 AM:
> I am not sure if it allows transaction pooling.

Well, take the time to figure it out. With transaction pooling enabled,
you can get away with a much lower number of server connections. For
example, our application regularly has thousands of clients connected to
pgbouncer and is quite happy with ~30 server connections (roughly the
core count of the db server). If we couldn't use transaction pooling
we'd be fighting with how to keep those thousands of connections from
wasting a bunch of resources on our db.

https://www.pgbouncer.org/features.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Lorusso Domenico 2023-07-08 15:06:29 How to add function schema in search_path in option definitio
Previous Message Rita 2023-07-08 11:27:10 Re: pgbouncer best practices