Re: Pgbouncer performance query

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: KK CHN <kkchn(dot)in(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Pgbouncer performance query
Date: 2026-01-22 12:35:30
Message-ID: CAFCRh-8jQSMEz2mfWXbGfu_mMdty2dJbR8uCNdACdeRjDc4s-g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jan 22, 2026 at 1:29 PM KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
> I agree when I have increased the concurrent connections to 300 (pgbench -c 300 ) then Direct hit on DB server fails with Error too many clients as follows

Just increase max_connections then:
https://www.postgresql.org/docs/current/runtime-config-connection.html#GUC-MAX-CONNECTIONS

Sounds like you should stick to direct PostgeSQL access, if pgBouncer
makes it 10x slower :). --DD

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nicolas Seinlet 2026-01-22 13:22:27 Re: pg_trgm upgrade to 1.6 led to load average increase
Previous Message KK CHN 2026-01-22 12:35:12 Pgbouncer performance query