pgBadger v11.0 released

Grenoble, France - June 25th, 2019

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

pgBadger 11.0 was released today, this release adds some major new
features and fixes some issues reported by users since the last four
months.

New features:

  - Regroup cursor related query (DECLARE,CLOSE,FETCH,MOVE) into new
    query type CURSOR.
  - Add top bind queries that generate the more temporary files.
    Require log_connection and log_disconnection be activated.
  - Add --exclude-client command line option to be able to exclude log
    entries for the specified client ip. Can be used multiple time.
  - Allow to use time only in --begin and --end filters.
  - Add -H, --html-dir option to be able to set a different path where
    HTML report must be written in incremental mode. Binary files stay
    on directory defined with -O, --outdir option.
  - Add -E | --explode option to explode the main report into one
    report per database. Global information not related to a database
    are added to the postgres database report.
  - Add per database report to incremental mode. In this mode there
    will be a sub directory per database with dedicated incremental
    reports.
  - Add support to Heroku's PostgreSQL logplex format. Log can be
    parsed using:

      heroku logs -p postgres | pgbadger -f logplex -o heroku.html -

  - When a query is > 10Kb we first limit size of all constant string
    parameters to 30 characters and then the query is truncated to 10Kb.
    This prevent pgbadger to waste time/hang with very long queries
    when inserting bytea for example. The 10Kb limit can be controlled
    with the --maxlength command line parameter.
    The query is normalized or truncated to maxlength value only after
    this first attempt to limit size.

This new release breaks backward compatibility with old binary or JSON
files. This also mean that incremental mode will not be able to read
old binary file. If you want to update pgBadger and keep you old reports
take care to upgrade at start of a new week otherwise weekly report will
be broken. pgBadger will print a warning and just skip the old binary
file.

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


===== Links & Credits =====

I would like to thank all users who submitted patches and users
who reported bugs and feature requests, they are all cited
the ChangeLog file.

pgBadger is an open project. Any contribution to build a better tool is
welcome. You just have to send your ideas, features requests or patches
using the GitHub tools or directly to pgbadger@darold.net.

Links :

* Download:  https://github.com/darold/pgbadger/releases/
* Support: use GitHub report tool at
https://github.com/darold/pgbadger/issues
  or contact pgbadger@darold.net.

For a complete list of commercial support near of your place take a look
at the PostgreSQL Professional Services page, they all do great job and
most of them can help you.
(http://www.postgresql.org/support/professional_support)

--------------

**About pgBadger** :

pgBagder is a new generation log analyzer for PostgreSQL, created by
Gilles Darold (also author of ora2pg, the powerful migration tool).
pgBadger is a fast and easy tool to analyze your SQL traffic and create
HTML5 reports with dynamics graphs. pgBadger is the perfect tool to
understand the behavior of your PostgreSQL servers and identify which
SQL queries need to be optimized.


Docs, Download & Demo at http://pgbadger.darold.net/

-- 
Gilles Darold