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 1tvF95-002ht3-Oc for pgsql-announce@arkaria.postgresql.org; Thu, 20 Mar 2025 12:37:12 +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 1tvF94-000Z4S-FL for pgsql-announce@arkaria.postgresql.org; Thu, 20 Mar 2025 12:37:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tvF92-000Z2o-U1 for pgsql-announce@lists.postgresql.org; Thu, 20 Mar 2025 12:37:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tvF90-0007ta-1k for pgsql-announce@lists.postgresql.org; Thu, 20 Mar 2025 12:37:08 +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=zddxCMNmVjNOUBtatcud7umDKPzBUQJ4hEkCc3YPAjA=; b=0k/Pfv8sOnaC/eFtb6FRWuimMn m7KxcDSwT1TtzukwKy4gPDxkDUUndLVUZoD5jLUh5qugyv2EYbVSr1hxCfbJdjcQcpmKhDThZTnoc EnhML7z4j/hljdaVmz8I2YWXuBhUM2LyJGypBJ8tOiGl1ws7ErlcrqmPrwLI6nQwezTzOum3eNBPf bsulSu4VyGW96HyoLh/yjkgIYPw5JbxMkMWGeS5FwFc7bNSsHs5cAv+iCnIdoyjc/zHhDxC/7s5j0 MZyc6rG6MX4z6kPoKglMGvUL9KIFUYB4H9qnK1aE7NwFEt5phkQaMz43MD7P8JRSRfv9MPpTd1zjj bpQ14DeA==; Received: from wrigleys.postgresql.org ([217.196.149.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 1tvF8z-00ADm1-NM for pgsql-announce@lists.postgresql.org; Thu, 20 Mar 2025 12:37: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 1tvF8x-0002iU-26 for pgsql-announce@lists.postgresql.org; Thu, 20 Mar 2025 12:37:03 +0000 Content-Type: multipart/mixed; boundary="===============8888637844046977174==" MIME-Version: 1.0 Subject: pgBadger v13.1 released To: PostgreSQL Announce From: HexaCluster via PostgreSQL Announce Reply-To: gilles@hexacluster.ai Date: Thu, 20 Mar 2025 12:36:30 +0000 Message-ID: <174247419002.674.13685729565192959601@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 2819016fcd3c47794c2ca67df06106c60f5a5b14f3fa71ef73a5b0f198dc5ecd List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8888637844046977174== Content-Type: multipart/alternative; boundary="===============6854188005457675503==" MIME-Version: 1.0 --===============6854188005457675503== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Antananarivo, Madagascar - March 17th, 2025 ## pgBadger pgBadger is a PostgreSQL performance analyzer, built for speed with fully detailed reports based on your PostgreSQL log files. pgBadger 13.1 was released today, this release fixes issues reported by users since last release and adds some new features: - Add new report about vacuum throughput with a graph about vacuum per table that consume the more CPU. The table output reports I/O timing read and write per table as well as the CPU time elapsed on the table. This patch also adds frozen pages and tuples to the Vacuums per Table report. - Add --no-fork option for debugging purpose to not fork processes at all. - Add millisecond to the raw csv output. - Add log filename to sample reports when multiple file are processed. 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/) --===============6854188005457675503== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pgBadger v13.1 released
 

pgBadger v13.1 released

Antananarivo, Madagascar - March 17th, 2025=

pgBadger

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

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

  • Add new report = about vacuum throughput with a graph about vacuum per table that consume the more CPU. The table output reports I/O timing read and write per table as well as the CPU time elapsed on the table. This patch also adds frozen pages and tuples to the Vacuums per Table report.
  • Add --no-fork o= ption for debugging purpose to not fork processes at all.
  • Add millisecond= to the raw csv output.
  • Add log filenam= e to sample reports when multiple file are processed.

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/.
 
--===============6854188005457675503==-- --===============8888637844046977174==--