Database Management

DPA PostgreSQL Long Running Query alert reports incorrect long runtimes

In DPA 2024.4 monitoring PostgreSQL 15, the “PostgreSQL Long Running Query” administrative alert may report queries as long running even though they have already completed. This behavior is a known product issue and is planned to be fixed in a future DPA release.

First published date

1/30/2026 12:52 PM

Last published date

1/30/2026 4:22 PM

Overview

Monitoring PostgreSQL v15 in DPA 2024.4 may show that the “PostgreSQL Long Running Query” alert triggers for many SQL statements that are no longer running, including small SELECT statements that are shown as running for over 8000 minutes. Direct checks against the database do not show timeouts or truly long‑running queries. DPA logs capture connectivity timeouts to the monitored PostgreSQL instance while executing several PostgreSQL alerts, including “PostgreSQL Long Running Query.”

Product section

Database Performance Analyzer

Cause

This has been identified as a known issue in DPA 2024.4.

Current DPA PostgreSQL process‑based alert logic can report stale/incorrect runtime information for queries under certain conditions. This leads to completed or short‑lived queries being flagged as long running, resulting in inaccurate alert notifications.

Resolution

A fix is planned for a future release of DPA. As of January 30, 2026, there are no workarounds. Watch this article for updates.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.