pgbouncer checks should perhaps exclude pgbouncer database

[phinjensen]

ID: 107 Version: 2.19.0 Date: 2012-07-10 07:19 EDT Author: Peter Eisentraut ([email protected])

---

Example, check that there are not less than 10 clients per database:

check_postgres --action=pgb_pool_cl_active -w 10 --reverse
POSTGRES_PGB_POOL_CL_ACTIVE WARNING: DB "pgbouncer" otherdb=53 | time=0.05s

Come to think of it, I don't know whether this output makes sense. With 2.16.0, it says

POSTGRES_PGB_POOL_CL_ACTIVE WARNING:  pgbouncer=1 | time=0.05

which is closer to the problem. Is it really useful to check the special "pgbouncer" database in these checks? It's easy to exclude them using --exclude=pgbouncer, of course.

[phinjensen]

Author: Peter Eisentraut ([email protected]) Date: 2012-07-10 07:23:41 EDT

---

--exclude=pgbouncer doesn't work with 2.19.0, but it does work with 2.16.0.