Postgres Enterprise Manager 10.6.0 release notes v10.6

Job Templates let a single job definition run across many agents instead of requiring a separate job per target. Import and export of Job Templates is also supported.

Browser-to-server credentials are now encrypted with RSA-OAEP: the server generates per-session RSA keypairs and the client uses the Web Crypto API, with un-decryptable ciphertext rejected as a bad request. Feature-gated via PEM_ENCRYPT_PASSWORDS_IN_TRANSIT, with an optional PEM_REQUIRE_TRANSIT_ENCRYPTION strict-enforcement mode. Operators can also supply a custom encryption key for the ASB password store, replacing the previously fixed key with an operator-controlled one.

Both alerts now consider per-table size rather than raw time-since-last-run, so noisy small tables no longer generate false positives while large tables with a genuine backlog surface promptly.

A format-aware log parser scans server log files continuously, detects and cleanly recovers from log rotation, and stores events in pemdata.server_log_severity_scan. Timestamp comparison is DateStyle-aware so both PostgreSQL and EPAS work correctly.

The tool connects read-only and analyzes memory, connections, WAL and checkpoints, autovacuum, planner settings, logging, background writer, JIT, and replication settings, producing a tiered terminal report as well as markdown, SQL, and JSON output. It is compatible with PostgreSQL 17 and EPAS, and is installed at /usr/edb/pem/maintenance_tool/bin/pem_advisor.

Scheduled reports can now be sent as HTML or JSON file attachments over SMTP, with the report rendered entirely in the database.

The PEM web tier can now maintain a single shared credential cache from a service keytab and connect to the PEM backend as a service principal, while PostgreSQL maps the SPN to a database role via pg_ident.conf and the DSN carries the end user in the user= field. Three new configuration keys — PEM_KRB_USE_SERVICE_TICKET, PEM_KRB_SERVICE_CACHE_NAME, and PEM_USER_KRB_INCLUDE_REALM — control the behaviour.

The probe and alert template surface has been updated to cover the new server version.

Encryption keys can now be supplied via PEM_ENC_FILE or PEM_ENC_SCRIPT, enabling key rotation via a key index embedded in the encrypted payload.

The "Purge deleted objects" job runs every 15 minutes and re-evaluates the deleted_objects_data_retention_time setting on each run, so changing the retention threshold also affects entities already awaiting purge. Children are drained in bounded batches before the parent row is removed, and cleanup covers both the pem catalog schema and the pemdata / pemhistory schemas.

New runtime requirements files ship for debian-13-amd64 and debian-13-arm64.

The endpoint now rejects mis-ordered thresholds (ascending required for the > operator, descending for <) on both newly added and modified alert configurations, catching mis-configurations at write time instead of at alert dispatch time.

The create dialog adds an "Internal name" field that auto-populates as cp_ plus a slug and is editable during creation (read-only afterwards). The cp_ prefix is mandatory and the remainder must match [a-z0-9_]+.

System jobs remain admin-only, and schedule exceptions (skip dates) are covered by the same scope.

New indexes on the agent_id and probe_internal_name columns speed up probe-target lookups.

Closed a race window in save_file that could allow a leaf symlink to redirect a save operation to an unintended path.

This removes the previous mismatch where the two intervals could drift apart under configuration overrides. You can still configure the heartbeat tolerance as in previous versions, but this now affect only the tolerance and not the underlying heartbeat intervals.

The REST API v17 endpoint now accepts any positive integer number of hours; the legacy endpoint still accepts the "N hour(s)" string form; and the UI field validates a minimum of 1. Operators can now schedule multi-day maintenance windows in a single blackout.

The default policy no longer includes 'unsafe-inline' or 'unsafe-eval'. Every inline script and style across base templates and tool-specific templates (Profiler, Dashboards, Cluster Topology, Reports, REST API docs, Barman) is now tagged with a per-request nonce. style-src retains 'unsafe-inline' to accommodate MUI runtime styles; 'unsafe-eval' is added only in DEBUG builds.

Tag-based filtering now behaves consistently across all node types. Previously agents were skipped by the filter and remained visible regardless of the selected tags.

These values are now converted to absolute paths during agent registration.

PGD 5 raft subgroups elect leaders independently, so the alert now includes node_group_name in the probe key columns, the data and history tables, the chart, and the alert template.

The wait-events timeline drill-down is also hardened against similar null cases.

Previously the tab could resolve to the wrong monitored server.

A subsequent update fixes any already-upgraded systems whose steps were left using SELECT.

Empty pattern arrays are no longer implicitly treated as wildcards.

The heartbeat thread now waits for the old thread to exit before recreating it, so two threads holding separate connections can no longer coexist.

The warning was harmless but polluted upgrade logs.

An empty field previously collapsed the varbinding; a NULL placeholder is now substituted instead.

The backend already silently rejected such edits; the SQL editor is now read-only for system probes so the UI affordance matches the actual permission.

These characters are now correctly escaped when substituted into webhook payloads.

Choosing Global + servers/agents now returns all matching alerts (previously only global alerts were returned); a Global selection no longer overrides other selections; Cleared alerts are preserved in the summary; and the output now includes target level, unit, and database/schema/object context columns.

The missing description now renders safely instead of aborting the page load.

The tooltip now shows the chart's description text.

The hardcoded OID and Definition-tab type restriction were removed and replaced with proper checks on both the inheritedfrom and inheritedfromtable gates. Foreign-table inline edit_types filtering is also fixed, along with readonly checks for attstattarget and attstorage. An ERD regression caused by the same issue was also corrected.

HTTP error response handling for webhook payloads now correctly reports non-2xx responses as failures.

When PEM_USER_KRB_INCLUDE_REALM is False, the realm is now stripped from the username used for role lookup, but the full principal is retained as the email so user validation succeeds.

Row expansion is now bound to row identity rather than display position.

Previously a restored tab could show the content from a different tab.

Probe lookup is now keyed on column name instead of position.

Deleted steps are now parked (marked as removed and disabled) so they disappear from the UI, while the job step log history survives for audit and troubleshooting.

The server sends exceptions as three arrays; these are now correctly converted for display when a job's properties are loaded, not only when saved. Also fixed saving exceptions on a newly-added schedule during a job update.

All BART references have been retired from the agent, server schema, web UI, and packaging.