# Percona PMM tool giving performance issues on Prod environments **URL:** \ **Category:** Percona Monitoring and Management (PMM)\ **Created:** [March 27, 2025, 3:17pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390 "2025-03-27T15:17:10Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![siddharth0204](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@siddharth0204](https://forums.percona.com/u/siddharth0204)\ **Post date:** [March 27, 2025, 3:17pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/1 "2025-03-27T15:17:10Z")
hello, Thanks for helping out on our issues. Recently when using PMM for our postgresql instance, we saw significant performance issue that took a toll on performance of the database because of below sql fired by PMM and we had to disable Percona service immediately SELECT current\_database() datname, schemaname, relname, seq\_scan, seq\_tup\_read, idx\_scan, idx\_tup\_fetch, n\_tup\_ins, n\_tup\_upd, n\_tup\_del, n\_tup\_hot\_upd, n\_live\_tup, n\_dead\_tup, n\_mod\_since\_analyze, COALESCE(last\_vacuum, ‘1970-01-01Z’) as last\_vacuum, COALESCE(last\_autovacuum, ‘1970-01-01Z’) as last\_autovacuum, COALESCE(last\_analyze, ‘1970-01-01Z’) as last\_analyze, COALESCE(last\_autoanalyze, ‘1970-01-01Z’) as last\_autoanalyze, vacuum\_count, autovacuum\_count, analyze\_count, autoanalyze\_count FROM pg\_stat\_user\_tables How can we take care of the above issue. Has anybody faced this issue before TIA Thanks and Regards, Siddharth ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [March 27, 2025, 8:35pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/2 "2025-03-27T20:35:25Z")
Hello @siddharth0204, what version of PMM? We have fixed many query-related issues in the past 2 years. Make sure you are on the latest version of PMM2. ---
**Author:** ![siddharth0204](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@siddharth0204](https://forums.percona.com/u/siddharth0204)\ **Post date:** [March 28, 2025, 12:57pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/3 "2025-03-28T12:57:10Z")
hi Matthew, Thanks for the response WE are using version PMMVersion: 2.41.1 Does this version have the fixes you are talking about Regards Siddharth ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [March 28, 2025, 6:34pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/4 "2025-03-28T18:34:16Z")
This query is a ‘custom’ query that we pre-install. > **[Percona Monitoring and Management - PostgreSQL](https://docs.percona.com/percona-monitoring-and-management/3/install-pmm/install-pmm-client/connect-database/postgresql.html)** > > How to set up PMM to monitor a PostgreSQL or Percona Distribution for PostgreSQL database instance. You can remove it if you’d like. ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [March 28, 2025, 8:45pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/5 "2025-03-28T20:45:41Z")
Hi, no, your version doesn’t include fix. Please update to the latest version. ---
**Author:** ![siddharth0204](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@siddharth0204](https://forums.percona.com/u/siddharth0204)\ **Post date:** [April 1, 2025, 1:59pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/6 "2025-04-01T13:59:34Z")
Thanks Matthew, Could you please let us know steps to remove this query from getting executed Regards, Siddharth ---
**Author:** ![nurlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/nurlan/32/1523_2.png) [@nurlan](https://forums.percona.com/u/nurlan)\ **Post date:** [April 4, 2025, 8:22am UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/7 "2025-04-04T08:22:20Z")
There should be few files in /usr/local/percona/pmm/collectors/custom-queries/postgresql, please find this query there and comment or remove yaml structure related to it. ---
**Author:** ![siddharth0204](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@siddharth0204](https://forums.percona.com/u/siddharth0204)\ **Post date:** [April 23, 2025, 3:26pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/8 "2025-04-23T15:26:04Z")
thanks much for your response. We will try the above solution and let you know how it goes Regards, Siddharth ---
**Author:** ![Bharath\_K](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/bharath_k/32/19613_2.png) [@Bharath\_K](https://forums.percona.com/u/Bharath_K)\ **Post date:** [February 19, 2026, 6:06pm UTC](https://forums.percona.com/t/percona-pmm-tool-giving-performance-issues-on-prod-environments/37390/9 "2026-02-19T18:06:26Z")
We are using PMM3 but the same query utilizing most of the CPU/Memory of the cluster. As per below instructions if we comment the query from .yml file and what is the impact of monitoring in PMM?