pgBadger 13.0 functions as a PostgreSQL performance analyzer, delivering comprehensive reports that are derived from log files. The update addresses several user-reported issues and introduces new features. The update enhances support for auto_explain plans in CSV and JSON log formats, introduces two additional options for defining inbound query and session histograms, and includes three LOG messages not reported as events. However, it creates a backward compatibility issue when utilized in incremental mode.

pgBadger 13.0 released

pgBadger is a PostgreSQL performance analyzer, built for speed with fully detailed reports based on your PostgreSQL log files.

pgBadger 13.0 was released today, this release of pgBadger fixes some reported by users since last release and adds some new features:

• Add two new option to be able to redefined inbound of query and session histogram.
• --histogram-query VAL: use custom inbound for query times histogram. Default inbound in milliseconds: 0,1,5,10,25,50,100,500,1000,10000
• --histogram-session VAL: use custom inbound for session times histogram. Default inbound in milliseconds: 0,500,1000,30000,60000,600000,1800000,3600000,28800000
• Add support of auto_explain plan for csv and json log formats.
• Add three LOG messages that was not reported as events: unexpected EOF, incomplete startup packet and detected deadlock while waiting for.

Backward compatibility issues:

• Change the way LOG level events reported in the Events reports are stored. Some of them was still reported and counted as errors instead as LOG level entries. The fix stores and reports them as EVENTLOG to differentiate them from queries. This change introduce a backward compatibility break when pgbadger is used in incremental mode. You will have the double behavior during the week of the upgrade.

For the complete list of changes, please checkout the release note on  https://github.com/darold/pgbadger/releases

pgBadger 13.0 released