RE: Pgbouncer discard all

[Scot Kreienkamp <Scot.Kreienkamp@xxxxxxxxxxxx>]

If they are visible in pg_stat_activity then yes.  Likewise, if they are only visible in pgbouncer, then no. 

 

The last query being discard all means that PGBouncer has returned the connection to the pool to make it available to the next client that needs it.  So what you’re seeing sounds to me like expected behavior. 

 

Scot Kreienkamp |Senior Systems Engineer | La-Z-Boy Corporate
One La-Z-Boy Drive| Monroe, Michigan 48162 | Office: 734-384-6403 | | Mobile: 7349151444 | Email: Scot.Kreienkamp@xxxxxxxxxxxx

From: Nicola Contu [mailto:nicola.contu@xxxxxxxxx]
Sent: Tuesday, October 16, 2018 11:12 AM
To: martin.marques@xxxxxxxxxxxxxxx
Cc: Scot Kreienkamp <Scot.Kreienkamp@xxxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx; Alessandro Aste <Alessandro.aste@xxxxxxx>
Subject: Re: Pgbouncer discard all

 

 2492534808 | dev    |   7355 | 1833427130 | pgbouncer       |                         | 10.151.2.145   |                 |       60570 | 2018-10-16 14:13:05.151015+00 |                               | 2018-10-16 15:10:40.309993+00 | 2018-10-16 15:10:40.310038+00 | Client

  | ClientRead          | idle   |             |              | DISCARD ALL

 

They are idle actually.

Will they count as client connection on the total amount set on the postgres.conf?

 

Il giorno mar 16 ott 2018 alle ore 16:22 Martín Marqués <martin.marques@xxxxxxxxxxxxxxx> ha scritto:

El 16/10/18 a las 09:59, Scot Kreienkamp escribió:
> Are you sure they’re actually waiting?  Don’t forget 10.5 will show the
> last query executed even if the connection is idle.  I believe discard
> all would be the last command the pgbouncer would send to the database
> when the client is done as it resets the connection for the next
> client.  So what you’re describing would seem to be expected behavior. 

He might have been referring to client waiting. That is visible in the
pgbouncer pseudo-database

OTOH if the the waiting is seen in pg_stat_activity, then pgbouncer has
nothing to do. The connection has already been assigned to the client
and the waiting is happening on the database server, not the pooler.

Regards,

--
Martín Marqués                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

This message is intended only for the individual or entity to which it is addressed.  It may contain privileged, confidential information which is exempt from disclosure under applicable laws.  If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information.  If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.