From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Discard All in pgbouncer
Date: Mon, 9 Oct 2023 08:22:01 -0600
Message-ID: <753F56B9-3E71-4CB7-91DC-70BF3C8E4EC7@elevated-dev.com> (raw)
In-Reply-To: <CAJk5AtbOeXVLDj5frFBy3Bw9xxja-bY1hcObMWonQ-xW-Oq=HQ@mail.gmail.com>
References: <CAJk5AtachHvTqeMT=Y+3wKaRgQnO8ypBUPvGQK4JFH5thkxcew@mail.gmail.com>
<CAAo1mbkLHPZYr7AGthoSg3pFf14LLNbEbZdCJUUoVxm6Bd1jjg@mail.gmail.com>
<CAJk5AtbOeXVLDj5frFBy3Bw9xxja-bY1hcObMWonQ-xW-Oq=HQ@mail.gmail.com>
> On Oct 9, 2023, at 8:18 AM, Rajesh Kumar <rajeshkumar.dba09@gmail.com> 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?
DISCARD ALL is simply the last query executed. There is no time period for it to "go away". It is the last query executed on that connection, and will remain the last query executed on that connection until another query is executed on that connection.
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: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, rajeshkumar.dba09@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Discard All in pgbouncer
In-Reply-To: <753F56B9-3E71-4CB7-91DC-70BF3C8E4EC7@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox