-
Notifications
You must be signed in to change notification settings - Fork 770
pg_replication_slots.active_pid does not exist #30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I forgot to include the error output: INFO[0000] Error running query on database: pg_stat_replication pq: column pg_replication_slots.active_pid does not exist source=postgres_exporter.go:624 |
Related to #29 We're probably past the point where we need to be enable/disable some of the checks. |
I'm inclined to factor out all the existing queries into the YAML file, giving the user full control. |
…for querying SHOW variables - this can generally be done by querying pg_settings instead. Fixes prometheus-community#29 and prometheus-community#30 upstream.
I'm not so enthusiastic about the YAML - the goal of the exporter is to try and be as plug and play as possible. The YAML is more a nod to the special cases when you need just a little bit more, but don't want an application specific exporter. |
Pull request #23 has introduced a regression: the query against pg_stat_replication now joins with pg_replication_slots on pg_stat_replication.pid=pg_replication_slots.active_pid. But pg_replication_slots.active_pid is not a valid column, see https://www.postgresql.org/docs/9.4/static/catalog-pg-replication-slots.html. In light of that and the fact that pg_replication_slots is only present in 9.4 (not in 9.2, 9.5, etc) I suggest reverting this change altogether.
The text was updated successfully, but these errors were encountered: