Re: Pgbouncer discard all

From: Martin Marques <martin(dot)marques(at)2ndquadrant(dot)com>
To: Nicola Contu <nicola(dot)contu(at)gmail(dot)com>
Cc: Scot(dot)Kreienkamp(at)la-z-boy(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org, Alessandro Aste <Alessandro(dot)aste(at)gtt(dot)net>
Subject: Re: Pgbouncer discard all
Date: 2018-10-16 15:33:56
Message-ID: da0275b1-93e7-deb0-dac1-a1e926902f1b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scot Kreienkamp 2018-10-16 15:35:30 RE: Pgbouncer discard all
Previous Message Nicola Contu 2018-10-16 15:12:24 Re: Pgbouncer discard all