| From: | Martín Marqués <martin(dot)marques(at)2ndquadrant(dot)com> |
|---|---|
| To: | Scot Kreienkamp <Scot(dot)Kreienkamp(at)la-z-boy(dot)com>, Nicola Contu <nicola(dot)contu(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Alessandro Aste <Alessandro(dot)aste(at)gtt(dot)net> |
| Subject: | Re: Pgbouncer discard all |
| Date: | 2018-10-16 14:22:04 |
| Message-ID: | f02b447e-c1e6-450b-8219-ede2053e264c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shrikant Bhende | 2018-10-16 14:29:24 | Re: FATAL: terminating connection because protocol synchronization was lost |
| Previous Message | Adrian Klaver | 2018-10-16 13:28:59 | Re: Compile psql 9.6 with SSL Version 1.1.0 |