La forma que uso para seguir el seguimiento de los clientes desde pgbouncer es unirme a pg_stat_statements con pgbouncer show clients dominio. Aquí hay un ejemplo:
t=# create extension "postgres_fdw";
CREATE EXTENSION
t=# CREATE SERVER pgbouncer FOREIGN DATA WRAPPER postgres_fdw OPTIONS ( host '10.10.10.10', port '6432', dbname 'pgbouncer');
CREATE SERVER
(Por supuesto, puede usar solo dblink o solo postgres_fdw; yo uso mix para admitir el uso obsoleto en prod... Si no tenía ninguna nota, simplemente ignórela...)
t=# create extension "dblink";
CREATE EXTENSION
t=# create view bnc_client AS SELECT _.type,
_."user",
_.database,
_.state,
_.addr,
_.port,
_.local_addr,
_.local_port,
_.connect_time,
_.request_time,
_.ptr,
_.link,
_.remote_pid,
_.tls
FROM dblink('pgbouncer'::text, 'show clients'::text) _(type text, "user" text, database text, state text, addr text, port integer, local_addr text, local_port integer, connect_time timestamp with time zone, request_time timestamp with time zone, ptr text, link text, remote_pid smallint, tls text);
CREATE VIEW
t=# create user mapping FOR vao server pgbouncer options (user 'pgbouncer_known_user', password 'password_here');
CREATE USER MAPPING
Ahora podemos unirnos a la vista de pgbouncer con pg_stat_statements :
t=# select
datname
, usename
, p.state
, case when b.user is not null then 'pgBouncer' else application_name end app
, case when b.user is null then client_addr else addr::inet end ip
, b.user
, b.state "bState"
, case when waiting then true else null end w
, b.connect_time
, query_start
, md5(query)::uuid
, pid
from pg_stat_activity p
left outer join bnc_client b
on addr||':'||b.port = regexp_replace(p.application_name,'^.{0,}(- )','')
where pid <> pg_backend_pid()
;
datname | usename | state | app | ip | user | bState | w | connect_time | query_start
| md5 | pid
---------+---------+-------+------------------------+--------------+------+--------+---+--------------+-------------------------------
+--------------------------------------+-------
dbn | usr | idle | | 192.168.0.1 | | | | | 2017-03-09 17:19:46.206643+00
| d1730c52-dffd-3650-a399-23f4dd4aa456 | 12614
dbn | usr | idle | app - 10.10.10.10:24514 | 10.10.10.10 | | | | | 2017-03-10 11:24:34.999174+00
| 92a0340c-9ecc-9375-37c0-e70e8b225db4 | 22563
(2 rows)
Aquí app - 10.10.10.10:24514 significa que este pid es de pgbouncer, y a pgbouncer se conectó desde 0.10.10.10
