Hi Daniel, sorry, for some reason, I never got your answeres, I think my mail provider might've flagged them and eventually discarded them :-/
On Sat, Jun 08, 2024 at 04:44:41PM +0200, Daniel Swarbrick wrote: > No sooner than I had posted my previous reply, I discovered that there is in > fact already an upstream PR for the aforementioned #547 [1]; unsurprisingly > #548 [2] claims to fix it, but has been awaiting approval since 2021 :( > > Perhaps you could give that PR a nudge, and perhaps it also makes sense if > we simply cherry-pick that as the Debian patch. > > [1]: https://github.com/prometheus-community/postgres_exporter/issues/547 > [2]: https://github.com/prometheus-community/postgres_exporter/pull/548 I can try, but I am not sure how much that helps; there are some other ones as well (#914 and #1048). But what makes it even worse is that they introduced a duplicate metric in master since, without removing this now apparently redundand (and broken) metric, see my comments to #1027. So I am not sure this is ever going to be fixed in unstable in a way that can be readily backported to stable. So I think pushing a minimal fix to stable still make sense. Michael
