From: pgAssistant dev team via PostgreSQL Announce <announce-noreply@postgresql.org>
To: PostgreSQL Announce <pgsql-announce@lists.postgresql.org>
Subject: pgAssistant 3.8.0 : continuous improvement loop for Postgres
Date: Wed, 16 Sep 2026 02:52:59 +0000
Message-ID: <178952717935.1256.3445053158444721743@wrigleys.postgresql.org> (raw)
With this release, pgAssistant is evolving beyond PostgreSQL analysis and tuning to become a **continuous PostgreSQL improvement platform**.
The new positioning is built around a **continuous improvement loop**:
Observe → Diagnose → Prioritize → Plan → Implement → Collect again → Measure
pgAssistant already helped identify what should be improved and turn recommendations into a prioritized Executive Plan with clear DEV and OPS ownership.
Combined with pgAssistant Collector, version 3.8.0 goes further by adding historical workload and environment measurements. The objective is to answer four essential questions:
- What should we improve?
- What did we decide to do?
- What did we actually change?
- What was the result?
Workload Insights compares consecutive collections and highlights:
- new and no-longer-detected recommendations;
- changes to the PostgreSQL version and configuration;
- workload evolution by statement type;
- changes in execution time and call volume;
- the queries with the greatest impact on the overall workload.
The ambition is to correlate the application of pgAssistant recommendations and the Executive Plan with observed performance changes.
Correlation is not causation, and a recommendation that is no longer detected does not necessarily prove that it was implemented. pgAssistant keeps these distinctions explicit while bringing the relevant evidence together in one place.
pgAssistant is not intended to replace real-time monitoring. Monitoring shows what is happening now; pgAssistant helps teams decide what to improve next, organize the remediation work, and measure what changed afterwards.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-announce@postgresql.org
Cc: announce-noreply@postgresql.org, pgsql-announce@lists.postgresql.org
Subject: Re: pgAssistant 3.8.0 : continuous improvement loop for Postgres
In-Reply-To: <178952717935.1256.3445053158444721743@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox