Context

• This is a replace to the Grafana fork of postgres_exporter, moving tracking from “exporter-package-v0.19.0” to “exporter-package-v0.19.1”.
• Pseudo-versions reference specific commits on the forked repo:
  • From: d256e52d0faf (2026-02-12)
  • To: 9c2c77e3702a (2026-02-25)
• Module path remains github.com/prometheus-community/postgres_exporter with replace to github.com/grafana/postgres_exporter.

Evidence reviewed

• This bump tracks a fork/branch rather than an upstream tagged release; no public semver release notes are available for the pseudo-version.
• The postgres_exporter project is primarily a “main” package; the Grafana fork’s “exporter-package” branch historically exposes light-weight library glue so exporters can be embedded/packaged. Patch-level branch bumps (0.19.0 → 0.19.1) typically suggest fixes rather than API reshapes.

Impact assessment

• Compile-time/API:
  • No major-version change or import path change.
  • No evidence of exported symbol changes between the two pseudo-versions was found via public releases; given the nature of the fork and a patch bump, compile-time API breakage is unlikely but should be verified with a build.
• Runtime/behavioral:
  • Potential areas to sanity-check in postgres_exporter updates:
    • CLI flags and env var defaults (e.g., query file handling, auto-discovery).
    • Metric set changes (added/removed metrics, label set adjustments).
    • Minimum supported PostgreSQL versions for specific collectors/queries.
  • If your packaging or integration depends on specific flags/behavior, run integration tests to verify no regressions in metrics or startup.

Code changes required

• None identified from the version bump itself.
• If your code imports library glue from the Grafana fork (e.g., an embedded runner or registration helper), a simple rebuild should confirm there are no signature changes. No diffs are proposed because no API changes are indicated.

Validation checklist

• Rebuild components that reference github.com/prometheus-community/postgres_exporter to confirm no compile-time breakage.
• Run a smoke test against a PostgreSQL instance:
  • Verify exporter starts with your existing configuration/flags.
  • Scrape and diff a sample of metrics to confirm expected metric names/labels are present.
  • Check logs for deprecations or flag changes.

References

• Fork: github.com/grafana/postgres_exporter
• Commits (for the pseudo-versions):
  • Old: d256e52d0faf
  • New: 9c2c77e3702a