pgBadger stops counting the same query execution twice
pgBadger 13.3 fixes duplicate counting when PostgreSQL logs the same execution through both log_min_duration_statement and auto_explain. The log analyzer also repairs multiline-statement handling and database-user filtering, and gives concurrent runs separate temporary filenames. These changes matter because a misleading report can send performance work toward queries that only appear unusually frequent because they were counted incorrectly.
HexaCluster · pgBadger · Nov 3, 2026
Why it matters
Before tuning a query from a report, make sure the collection and parsing pipeline represents executions correctly.
More context
Try the released maintenance version against a representative saved log and compare counts with your previous report. It also filters remote logs on the remote host in watch mode, reducing unnecessary transfers. Installation and download guidance is linked from the announcement.
Keep in mind
pgBadger analyzes the logs it receives; missing events or unsuitable logging settings still limit its view. A parser fix does not establish why an individual query is slow.
Original read