Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKLdY-008A3I-Vt for pgsql-announce@arkaria.postgresql.org; Sun, 08 Dec 2024 18:04:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tKLdW-002MhV-FZ for pgsql-announce@arkaria.postgresql.org; Sun, 08 Dec 2024 18:04:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKLbd-001z7l-Fx for pgsql-announce@lists.postgresql.org; Sun, 08 Dec 2024 18:02:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKLbb-001hWX-1u for pgsql-announce@lists.postgresql.org; Sun, 08 Dec 2024 18:02:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=uqbK88R2K9nMX8JZttvu6fw9+AozjExujlNpH5yRKTA=; b=K2K8sgAcR5y3gYRfNOlqKh3oz/ GZsywpbgjS3XjdkyM3VgDmdyJM6zJL9kZ7xy7sQ51zfGCCbNqjGx8+0TBusJ4+hHitYZHHiU9OSd9 wIe/X+iqn1D12cgEN+fpGhGdw4Z6myi8Rtdp/0yGOVGWXKfRrJh1sNyOmXt2gzPYv22YanGmYVg1E g6ThZOmdB/sx3fzTmSjx9kuT4VWrjkRNb7p9ZCPHfTjoPhtX5E+VaiFBvrZpc6svHmHfndxJpGZes 7KqmfbKZvVMrgkwX65TKxBKrBkaXIemSNpXVsTVKIIt1DICzorfeZEzSlD70+RPG//m+ElYHYqSgV 1P7CBg2g==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tKLbZ-005GZ1-4y for pgsql-announce@lists.postgresql.org; Sun, 08 Dec 2024 18:02:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tKLbW-00FboY-Kg for pgsql-announce@lists.postgresql.org; Sun, 08 Dec 2024 18:02:03 +0000 Content-Type: multipart/mixed; boundary="===============2201452170601991651==" MIME-Version: 1.0 Subject: pgBadger 13.0 released To: PostgreSQL Announce From: HexaCluster via PostgreSQL Announce Reply-To: gilles@hexacluster.ai Date: Sun, 08 Dec 2024 18:01:48 +0000 Message-ID: <173368090851.2556777.10046883875917203449@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 793836f9244272ae04711f8f575ae516b26ac56c80d9ccbc6ae2e188d0027a4d List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============2201452170601991651== Content-Type: multipart/alternative; boundary="===============4297227467202852850==" MIME-Version: 1.0 --===============4297227467202852850== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Vientiane, Laos - December 8th, 2024 ## pgBadger 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 histog= ram. Default inbound in milliseconds: `0,500,1000,30000,60000,600000,180000= 0,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](https://github.com/darold/= pgbadger/releases) ## 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: [http://pgbadger.darold.net/](http://pgbadger.darold.net/) * Support: use GitHub report tool at [https://github.com/darold/pgbadger/is= sues](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](http://www.postgresql.org/support= /professional_support) page, they all do great job and most of them can help you. -------------- **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/](http://pgbadger.daro= ld.net/) --===============4297227467202852850== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pgBadger 13.0 released
 

pgBadger 13.0 released

Vientiane, Laos - December 8th, 2024

pgBadger

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

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

  • Add two new opt= ion to be able to redefined inbound of query and session histogram.
  • --histogr= am-query VAL: use custom inbound for query times histogram. Default inbound in milliseconds: 0,1,5,10,25,50,100,500,1000,100= 00
  • --histogr= am-session VAL: use custom inbound for session times histogram. Default inbound in milliseconds: 0,500,1000,30000,60000,600000,1= 800000,3600000,28800000
  • Add support of = auto_explain plan for csv and json log formats.
  • Add three LOG m= essages that was not reported as events: unexpected EOF, incomplete startup packet and detected deadlock whil= e 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 ch= eckout the release note on https://github.com/darold/pgbadger/rel= eases

Links & Credits

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

pgBadger is an open project. Any contributi= on 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 :

For a complete list of commercial support n= ear of your place take a look at the PostgreSQL Professional= Services page, they all do great job and most of them can help you.

About pgBadger :

pgBagder is a new generation log analyzer f= or 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/
This email was sent to you from HexaCluster. It was delivered on their beha= lf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to HexaCluster.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============4297227467202852850==-- --===============2201452170601991651==--