public inbox for [email protected]  

help / color / mirror / Atom feed

From: hubert depesz lubaczewski <[email protected]>
To: Raj <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Pgbouncer
Date: Thu, 11 Sep 2025 15:55:22 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJk5Atanc-d4xg_3UxbTybvNmPfb593WAhLFqjAWEUhm5cYQDQ@mail.gmail.com>
References: <CAJk5Atanc-d4xg_3UxbTybvNmPfb593WAhLFqjAWEUhm5cYQDQ@mail.gmail.com>

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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Pgbouncer
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox