# pgBadger 13.3 fixes double-counting bug, adds auto_explain plan support

> **Key takeaway:** pgBadger 13.3 resolves a long-standing accuracy issue where queries logged by both log_min_duration_statement and auto_explain were counted twice, while adding support for query parameters and explain plan copying.

**Published:** 2026-11-03T16:03:55.660068+00:00 
**Source:** PostgreSQL Official News 
**Category:** databases-storage 
**Canonical URL:** https://fosswire.org/news/pgbadger-133-fixes-double-counting-bug-adds-autoexplain-plan.html 

## Summary
pgBadger 13.3, a maintenance release of the popular PostgreSQL log analyzer, addresses multiple user-reported bugs and adds incremental features for database operators analyzing query performance. The release fixes a significant double-counting bug where the same query execution could be reported by both log_min_duration_statement and auto_explain, inflating performance metrics. It also introduces support for handling "Query Parameters" from auto_explain output, adds explain plan copying functionality, and improves graph interactivity for reports with many items.

Additional fixes target the --explode option, multiline statement parsing, --dbuser filtering accuracy, and concurrent execution safety through per-run temporary file naming. Remote log filtering in watch mode now prevents unnecessary full log imports when monitoring remote hosts.

## What changes in pgBadger 13.3
- **Query deduplication:** Fixes the same execution being counted twice when both log_min_duration_statement and auto_explain log the same query, correcting inflated slow-query statistics.
- **Graph UI improvements:** Legend and mouseover graphs now support scrolling when item lists exceed 10 entries, improving usability for busy servers.
- **Concurrent execution safety:** Temporary dblist and last-parsed files now use per-run names, preventing race conditions when multiple pgBadger instances execute simultaneously.
- **Filtering and parsing fixes:** Resolves --explode option issues, multiline statement parsing problems, and incorrect query dropping when using --dbuser filtering.

## Why it matters
For PostgreSQL database administrators and SREs relying on accurate query performance telemetry, the double-counting fix eliminates a common source of misleading slow-query reports that could drive incorrect optimization decisions. The auto_explain enhancements strengthen pgBadger's integration with PostgreSQL's built-in query analysis tooling, making it more viable as a central performance monitoring solution in open-source database operations stacks.