Re: Discard All in pgbouncer

From: Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Discard All in pgbouncer
Date: 2023-10-09 14:22:55
Message-ID: CAJk5AtYQTC2bc3Sba=r+LqjNa=XZuV7HnSqoNPbtoOm7t3TWkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Purpose of bouncer is handle idle connections right? Is there a time period
for the DISCARD ALL to go away? If so, how to configure?

The part I don't understand is if bunch of connections in the name of
Discard all is idle , what difference it make?

If I have set Max conn in db as 250....do I have to set the same in
pgbouncer?

On Mon, 9 Oct 2023, 19:46 Ron, <ronljohnsonjr(at)gmail(dot)com> wrote:

> On 10/9/23 09:07, Rajesh Kumar wrote:
>
> Hi,
>
> I could see queries like DISCARD ALL is idle for more than 5minutes (we
> are using pgbouncer).
>
> Why is it idle for more than 5mns? I read about pgbouncer and could not
> understand this thing. If resetting a connection using query becomes one
> idle connection, I don't understand the pooling system here
>
>
> In your case, "Idle" just means that DISCARD ALL was the last statement
> that the pid executed. Now, it's just doing *nothing*, because there's
> nothing to do. IOW, this is just fine. No need to worry.
>
> --
> Born in Arizona, moved to Babylonia.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Michael Banck 2023-10-09 14:34:45 Re: Discard All in pgbouncer
Previous Message Scott Ribe 2023-10-09 14:22:01 Re: Discard All in pgbouncer