Re: Discard All in pgbouncer

You're */still/* missing the point.  If pgbouncer doesn't need to use a
connection, then... it's going to sit there "idle". That's what "idle" means!

What we haven't explicitly stated, but implied, is that pg_stat_activity
*does not* clear the query field when the status = 'idle'.  Thus, as we've
said before, DISCARD ALL /*was*//**/ the last statement to be executed.

On 10/9/23 09:18, Rajesh Kumar wrote:
> 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?
>
> On Mon, 9 Oct 2023, 19:42 Samed YILDIRIM, <samed(at)reddoc(dot)net> wrote:
>
> Hi Rajesh,
>
> DISCARD ALL is the query that is executed by PgBouncer in order to
> sanitise a database session before assigning it to another client. If
> you see this query in pg_stat_activity and status of the session is
> idle, most probably it is ok. Probably what you see is the last
> executed query for the session. And the session is idle and waiting to
> be assigned to a client. :)
>
> Best regards.
> Samed YILDIRIM
>
> On Mon, 9 Oct 2023, 17:07 Rajesh Kumar, <rajeshkumar(dot)dba09(at)gmail(dot)com>
> 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
>
> Plz help
>

--
Born in Arizona, moved to Babylonia.