# PMM Query Analytics Support for EDB Postgres Advanced Server (EPAS) 17/18

**URL:** <https://forums.percona.com/t/pmm-query-analytics-support-for-edb-postgres-advanced-server-epas-17-18/40900>\
**Category:** Uncategorized\
**Created:** [June 11, 2026, 6:36am UTC](https://forums.percona.com/t/pmm-query-analytics-support-for-edb-postgres-advanced-server-epas-17-18/40900 "2026-06-11T06:36:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ly\_Kimmeng](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ly_kimmeng/32/23228_2.png) [@Ly\_Kimmeng](https://forums.percona.com/u/Ly_Kimmeng)\
**Post date:** [June 11, 2026, 6:36am UTC](https://forums.percona.com/t/pmm-query-analytics-support-for-edb-postgres-advanced-server-epas-17-18/40900/1 "2026-06-11T06:36:03Z")

</div>

Title: PMM Query Analytics Support for EDB Postgres Advanced Server (EPAS) 17/18

Hi Percona Team,

We are planning to integrate EDB Postgres Advanced Server (EPAS) 17/18 with PMM and would like to understand the supported options for Query Analytics (QAN).

Our questions are:

1. Is EDB Postgres Advanced Server (EPAS) 17/18 officially supported by PMM for PostgreSQL monitoring and Query Analytics?

2. Can PMM Query Analytics work using only the standard PostgreSQL `pg_stat_statements` extension on EPAS?

3. If `pg_stat_statements` is supported, what are the limitations compared to using `pg_stat_monitor`?

4. Is Percona’s `pg_stat_monitor` extension supported and compatible with EPAS 17 and EPAS 18?

5. Does PMM support EDB’s `edb_stat_monitor` extension as a Query Analytics data source, or does PMM only recognize `pg_stat_statements` and `pg_stat_monitor`?

6. If `edb_stat_monitor` is not supported, is there a recommended approach for achieving equivalent Query Analytics functionality on EPAS?

7. Are there any additional extensions, configuration parameters, or known limitations when monitoring EPAS compared to PostgreSQL Community Edition?

Our primary goal is to use PMM dashboards and Query Analytics to monitor query performance, identify expensive SQL statements, analyze wait events, and perform performance troubleshooting on EPAS environments.

We would appreciate any guidance, best practices, or real-world experiences from users who have successfully integrated EPAS with PMM.

Thank you.

---

<div class="post-metadata">

**Author:** ![Agustin\_G](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/agustin_g/32/14111_2.png) [@Agustin\_G](https://forums.percona.com/u/Agustin_G)\
**Post date:** [July 28, 2026, 2:03am UTC](https://forums.percona.com/t/pmm-query-analytics-support-for-edb-postgres-advanced-server-epas-17-18/40900/2 "2026-07-28T02:03:50Z")

</div>

Hi @Ly_Kimmeng,

PMM QAN can be run in any PostgreSQL instance in which you have pg\_stat\_statements. It does not, however, support any EDB-specific functionality. Using pg\_stat\_statements is the correct way to go in this case.

You can read more about pg\_stat\_monitor functionality (to compare against what pg\_stat\_statements offers) in [Usage - Percona Query Performance Monitoring for PostgreSQL](https://docs.percona.com/pg-stat-monitor/user_guide.html#features)

I have not tried EPAS on PMM, so I can’t mention anything in that regard in particular, but you should definitely try it out (I don’t see any major roadblocks if EPAS behaves in an upstream-compatible way).