I am asking should we use pgbouncer? If so, what's the compelling situation despite having postgres inbuilt timeout parameters.
On Thu, 11 Sept 2025, 19:25 hubert depesz lubaczewski, <depesz@xxxxxxxxxx> wrote:
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
