Re: pgbouncer best practices

From: Rita <rmorgan466(at)gmail(dot)com>
To: Ben Chobot <bench(at)silentmedia(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-09 13:27:57
Message-ID: CAOF-KfjaXr-nzruThPjRyiie9Zs46pEy_gRTFEHuV3ynWz_mEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the tips. So far, I am very happy with PGbouncer. Just increased
number of db connections. Great piece of software!

Is there a way to see how many queued connections there are? Looking at the
stats I can't seem to figure that out.

On Sat, Jul 8, 2023 at 9:46 AM Ben Chobot <bench(at)silentmedia(dot)com> wrote:

> 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
>

--
--- Get your facts first, then you can distort them as you please.--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-07-09 14:22:02 Re: now() literal in pg_input_is_valid
Previous Message jian he 2023-07-09 12:13:13 now() literal in pg_input_is_valid