Re: Pgbouncer discard all
Martin Marques <martin.marques@2ndquadrant.com>
From: Martin Marques <martin.marques@2ndquadrant.com>
To: Nicola Contu <nicola.contu@gmail.com>
Cc: Scot.Kreienkamp@la-z-boy.com, pgsql-general@lists.postgresql.org,
Alessandro Aste <Alessandro.aste@gtt.net>
Date: 2018-10-16T15:33:56Z
Lists: pgsql-general
El 16/10/18 a las 12:12, Nicola Contu escribió: > 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? Yes, but that's the idea of having a pooler in between the app and the server. Whenever the app needs a new connection it will reuse one from the pool, instead of having to open a new connection. pgbouncer will eventually close the connection if it stays in the pool for longer than server_lifetime or server_idle_timeout. Regards, -- Martín Marqués http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services