Known issues

These are the currently known issues and limitations identified in the WarehousePG Enterprise Manager (WEM) release. Where applicable, we've included workarounds to help you mitigate the impact of these issues. These issues are actively tracked and are planned for resolution in a future release.

Deployment & infrastructure

• Each WEM deployment is designed to manage and monitor only one WarehousePG (WHPG) cluster. Managing multiple clusters requires separate, dedicated WEM installations for each.
• WEM can't be installed on Red Hat Enterprise Linux 7. This restriction applies only to the host running the WEM application; WEM is fully capable of monitoring WHPG clusters running on RHEL 7 nodes.

Query monitoring

• Cancelling an idle in transaction session from the Query Monitoring panel doesn't release the blocking transaction. WEM uses pg_cancel_backend, which terminates the user's connection but leaves the transaction open. The blocked queries remain in a waiting state until the transaction is manually cleaned up.

  Workaround: Connect to the cluster using psql and run SELECT pg_terminate_backend(<pid>) to forcibly close the blocking session and release its locks.

Access management

• The pg_hba.conf tab displays a security notice warning about trust-based authentication rules. Some of these rules are created automatically by gpinitsystem during cluster initialization. Modifying them can break internal WHPG communication and make the cluster unavailable. Review any proposed changes carefully before applying them.

• The HBA Editor may fail to locate the pg_hba.conf file and display the error Could not read pg_hba.conf: open <path>/pg_hba.conf: no such file or directory. This occurs when the file path doesn't match the expected coordinator data directory location.

  Workaround: Verify that the COORDINATOR_DATA_DIRECTORY environment variable is correctly set on the host running WEM.