https://percona.community/categories/pg_stat_monitor/Recent content in Pg_stat_monitor on Percona CommunityHugoen-us© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.Mon, 19 Oct 2026 00:00:00 +0000https://percona.community/blog/2026/10/19/pg-stat-monitor-2-4-0/Mon, 19 Oct 2026 00:00:00 +0000https://percona.community/blog/2026/10/19/pg-stat-monitor-2-4-0/<p>pg_stat_monitor started as a fork of pg_stat_statements, built to be a more advanced replacement for it. It provides more detailed information about query execution and groups it in configurable time buckets, so you can look at what happened in a particular time window. It also powers the Query Analytics feature in Percona Monitoring and Management (PMM). However, over time other work took priority at Percona, and the extension stopped getting the attention it needed. The original developers moved on to other things, and the reasoning behind several design decisions went with them. For a couple of years it stayed in maintenance mode, we were fixing reported bugs, and never stepped back to look at deep architectural issues. All that led to a degraded user experience and stability issues.</p>