Postgresql Exporter Connections
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Smart Checklist
Activity
Show:

Aaditya Dubey October 11, 2022 at 6:57 AM
Hi ,
Thank you for the confirmation.
Closing the ticket as stated.

Momo October 10, 2022 at 4:58 PM
Yes it can be closed

Aaditya Dubey October 10, 2022 at 2:13 PM
Hi ,
Thank you for the updates.
Please let us know if this report can be closed.

Momo October 3, 2022 at 7:45 AM
Hello all,
Thanks for the effort made in upgrading the postgres exporter, there is no longer intermittent when using localhost based connection.
Only 10 connections, in pooling. Which is great.
Thanks a lot !

Roma Novikov May 3, 2022 at 7:17 AM
Hi !
Thanks for the report and investigation against the latest version of the exporter! Looks like this problem can go away when we'll implement
Done
Created May 2, 2022 at 10:22 AM
Updated November 13, 2024 at 9:48 AM
Resolved October 11, 2022 at 6:58 AM
Hello all,
I am trying implement PMM across several postgres databases, and discovered that they were multiple connections instead of reusing as follows. Causing lots of log entries in postgres logs when connection log is enabled.
And found out using autodiscover with unix socket does not properly connect to the DBs, dunno if it's possible to update the DATA_SOURCE_NAME manually. Or disabling it simply to avoid this.
Which causes a lots of log entries in system journal (pmm-agent logs)
Also checked with the latest exporter from prometheus i do not see such behaviour when connecting to the DB connections remains stable. 1 connection per DB which seems ok.
Seems this exporter is tad behind than upstream.
Thanks a lot for this wonderful tool
Best Regards