Horton

Re: Pgbouncer discard all

Martin Marques <martin.marques@2ndquadrant.com>

View thread View on postgr.es
From: Martín Marqués <martin.marques@2ndquadrant.com>
To: Scot Kreienkamp <Scot.Kreienkamp@la-z-boy.com>, Nicola Contu <nicola.contu@gmail.com>, "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Cc: Alessandro Aste <Alessandro.aste@gtt.net>
Date: 2018-10-16T14:22:04Z
Lists: pgsql-general 
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