uspen

GCS please!

That is unnecessary. But if you need to request for example pg_stat_user_tables you need connect to custom db

--extend.query-path=custom.queries.yaml TPS - xact_commit in pg_stat_database QPS - calls in pg_stat_statements

QPS is COUNTER, so just `irate`

`master: true`

Now way I think. I use pgbouncer/database.ini ``` db1_user1 =host=db1.example.com dbname=db1 user=user1 db2_user1 =host=db1.example.com dbname=db2 user=user1 ``` pgbouncer/userlist.txt ``` "db1_user1" "pass1" "db2_user1" "pass2" ``` pgbouncer/pg_hba.conf ``` host db1_user1 db1_user1 0.0.0.0/0...

Nice! But, where elephant?

We also encountered this after switching from pgbouncer about 2 years ago

up

UP