Re: Pgbouncer

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Raj <rajeshkumar(dot)dba09(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Pgbouncer
Date: 2025-09-11 13:55:22
Message-ID: aMLUyeo6Ezy3cW0G@depesz.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Sep 11, 2025 at 07:01:26PM +0530, Raj wrote:
> We are migrating from oracle.to postgres and its done.
>
> Now as a DBA, to improve performance say idle connecting handling or
> anything, if I want to recommend pgbouncer to the team, what's the
> compelling reason would it be?

https://www.depesz.com/2012/12/02/what-is-the-point-of-bouncing/

> I may ask them to handle connections from application end and they may say
> ok but we still.may see idle connections are not closed.
>
> So, at point and for what compelling reason I should tell my manager, we
> must go-ahead and use etc.
>
> We use pg17 and in postgres itself I know idle_session_timeount,
> transaction_timeout, statement_timeout. Is this enough? Will it abruptly
> kill queries and if so, isn't it bad?

statement_timeout and transaction_timeout have the power to kill
queries, yes.

Best regards,

depesz

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron Johnson 2025-09-11 16:21:35 Allow connections by IP address?
Previous Message Raj 2025-09-11 13:31:26 Pgbouncer