Postgres Enterprise Manager 10.2.0 release notes v10.2
Released: 14 August 2025
New features, enhancements, bug fixes, and other changes in Postgres Enterprise Manager 10.2 include the following:
Highlights
- New alerts for failover events
- Automatically disable redundant alerts on replicas
- PEM can now run in FIPS-enabled environments
- Support for monitoring EDB Postgres Distributed 6
Enhancements
Description | Addresses |
---|---|
Added alert support for EFM/Patroni failover events.PEM now provides a built-in alert for failover in EFM and Patroni clusters. | |
The 'Last Vacuum' and 'Last AutoVacuum' alerts are now disabled automatically on replica nodes.PEM will no automatically disable the 'Last Vacuum' and 'Last AutoVacuum' alerts on servers which are currently physical replicas of a primary. This ensures you do not get duplicate alerts in primary/standby clusters. | |
Added new probes `bdr_node_group_config_summary` and `bdr_analytic_slot_name` for EDB Postgres Distributed 6; updated the `bdr_node_summary` probe to include the `node_uuid` column. | |
Added a new column `parent_table_name` to the `oc_table` probe to indicate partitioned/parent table relationships. | |
Introduced new config item | |
Introduced dynamic naming for the Monitoring panel.The text displayed in the tab for monitoring panels is now a descriptive name based on the contents of the panel. This makes it easier to navigate with multiple panels open. | |
Enhanced line chart tooltips to display seconds in timestamp values. | |
Upgraded HTTPD to 2.4.65 for PEM Windows installer. | |
Added self-diagnostic queries to the System Configuration report. | |
Enabled Markdown formatting in chart description tooltips. | |
PEM will now preserve the SSL port, SSL certificate path, and ServerName when upgrading or reconfiguring PEM.This change allows users to change these parameters to suit their environment without having them overwritten during PEM upgrade. |
Changes
Description | Addresses |
---|---|
Removed MD5 implementation from the PEM agentRemoved some unused code from the PEM Agent which implemented the MD5 hash algorithm. | |
Renamed heartbeat_interval to heartbeat_tolerance and changed the behavior be easier to understand.In prior versions of PEM, the We have replaced the setting with When upgrading to PEM 10.2, your previous settings will be respected and converted into an equivalent | |
Removed support for PostgreSQL and EPAS versions older than 11 from the Alternate Code tab in Manage Probes. | |
Changed the `unregister-server` CLI option from using the `--server-addr` to `--asb-host-name` for consistency. |
Bug Fixes
Description | Addresses |
---|---|
Resolved server registration issues caused by missing ssl column in the pem.server table (affecting PEM 10.1.1). | |
Fixed an issue whereby the 'primary' tag would appear on PGD servers rather than the PGD-specific tags. | |
Fixed a validation error when using comma-separated emails in Email Groups. | |
Addressed UI issues with MFA in PEM 10.Addressed multiple issues whereby the MFA UI was not rendering correctly and was therefore difficult or impossible to use. | |
Fixed duplication of existing entries when adding/deleting new entries in Email Groups. | |
Resolved an issue with the Delete button malfunctioning after adding a new Email Group. | |
Fixed an issue whereby the Patroni Cluster Status probe could write data to PEM for non-Patroni servers. | |
Fixed an issue whereby libpq5 was not installed during PEM configuration despite being required. | |
Fixed an issue whereby the Streaming Replication dashboard couldn't be opened on Patroni servers. | |
Fixed an issue with Patroni DCS health state reporting where the health status was incorrectly set to false when no leader was found or when the Patroni node list was empty. | |
Fixed an issue that disabled toggle buttons and time frequency settings on Manage Alerts | |
Fixed an issue where an invalid EFM installation path or cluster name would not result in an error or warning in PEM agent logs. | |
Fixed an issue preventing users from modifying data retention settings for system probes via the Manage Probes panel. | |
Fixed an issue with the database restriction feature by updating the field name from `db_restriction` to `db_res`. | |
Fixed a Windows build issue caused by an unsupported function in the Patroni probe | |
Resolved agent registration errors caused by missing agent.cfg, which led todefault value issues and unknown agent entries when using force-registration option | |
Updated SQL for Pie Chart settings to remove dashboard-level setting support, fixing color update issues | |
Fixed an issue which caused an incorrect chart title and missing pie chart color selection during data load. | |
Added missing Y-axis labels on Bar Charts. | |
Enabled the Download button by default in the Alert History dialog. | |
Removed redundant error icons in charts. | |
Fixed threshold-related errors in cmtemplate table charts. | |
Fixed an issue where errors would appear when chart data was empty. | |
Reduced redundant API calls to `server_versions` and added pagination for the Alternate Code table. | |
Corrected alert selection UI and toggle switch behavior for disabled webhooks | |
Fixed synchronization issues in chart colors, ensuring consistent color application across charts. | |
PEM will now stop uWSGI and clean NGINX config when uninstalling PEM in NGINX mode. | |
Added libjpeg dependency for PEM server runtime. | |
Fixed charts in Streaming Replication dashboard based on Server Replication properties | |
Fixed an issue where the audit configuration job was not getting created. | |
Fixed an issue where Capacity Manager report generation was failing. | |
Fixed an issue with interval calculation in Custom Probes. | |
Updated the Patroni timeline mismatch alert template query to handle empty string values properly. | |
Fixed an issue where the streaming replication dashboard could be opened even when a server lacks streaming replication data. | |
Updated the initial data check API for the streaming replication dashboard to conditionally check different monitoring tables based on the server's replication solution type. |
- On this page
- Highlights
- Enhancements
- Changes
- Bug Fixes