pgBadger v11.2 has been released - Mailing list pgsql-announce

From Gilles Darold
Subject pgBadger v11.2 has been released
Date
Msg-id f3a9afff-012f-8422-b78e-fa3facbc6472@darold.net
Whole thread Raw
List pgsql-announce
Grenoble, France - Marsh 17th, 2020

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

pgBadger 11.2 was released today, this release of pgBadger fix several
issues reported by users since past six months. It also adds some new
features:

  * Add support and autodetection of AWS redshift log format.
  * Add support to pgbouncer 1.11 new log format.
  * Handle zstd and lz4 compression format
  * Allow to fully separate statistics build and HTML report build in
    incremental mode without having to read a log file. For example
    it is possible to run pgbadger each hours as follow:
   
        pgbadger -I -O "/out-dir/data" --noreport /var/log/postgresql*.log
   
   It just creates the data binary files in "/out-dir/data" then
   for example you can make reports each night for the next day in
   a separate directory `/out-dir/reports`:
   
        pgbadger -I -l "/out-dir/data/LAST_PARSED" -H "/out-dir/reports"
/out-dir/data/2020/02/19/*.bin
   
    This require to set the path to the last parsed information, the
    path where HTML reports will be written and the binary data file
    of the day.

There is also new command line options:

  * Add new command line option --explain-url used to override the url
    of the graphical explain tool. Default URL is:
   
        http://explain.depesz.com/?is_public=0&is_anon=0&plan=
   
    If you want to use a local install of PgExplain or an other tool.
    pgBadger will add the plan in text format escaped at the end of
    the URL.

  * Add new option --no-week to instruct pgbadger to not build weekly
    reports in incremental mode. Useful if it takes too much time and
    resources.

  * Add new command line option --command to be able to set a command
    that pgBadger will execute to retrieve log entries on stdin.
    pgBadger will open a pipe to the command and parse log entries
    generated by the command. For example:
   
      pgbadger -f stderr --command 'cat /var/log/postgresql.log'
   
    which is the same as executing pgbadger with the log file directly
    as argument. The interest of this option is obvious if you have to
    modify the log file on the fly or that log entries are extracted
    from a program or generated from a database. For example:
   
      pgbadger -f csv --command 'psql dbname -c "COPY jrn_log TO STDOUT
(FORMAT CSV)"'
   
  * Add new command line option --noexplain to prevent pgBadger to
    parse and report explain plan written to log by auto_explain
    extension. This is useful if you have a PostgreSQL version < 9.0
    where pgBadger generate broken reports when there is explain plan
    in log.

Backward compatibility:

  - By default pgBadger will truncate queries up to 100000 characters.
    This arbitrary value and can be adjusted using option --maxlength.
    Previous behavior was to not truncate queries but this could
    lead in excessive resources usage. Limiting default size is safer
    and the size limit might allow no truncate in most cases. However
    queries will not be beautified if they exceed 25000 characters.

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
http://www.darold.net/




pgsql-announce by date:

Previous
From: Stefan Fercot
Date:
Subject: check_pgbackrest 1.8 has been released
Next
From: "Andreas 'ads' Scherbaum"
Date:
Subject: German PostgreSQL Conference 2020 is cancelled