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.96) (envelope-from ) id 1x6flm-000NA2-1m for pgsql-announce@arkaria.postgresql.org; Wed, 16 Sep 2026 02:53:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x6fll-004ACi-2v for pgsql-announce@arkaria.postgresql.org; Wed, 16 Sep 2026 02:53:09 +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.96) (envelope-from ) id 1x6flk-004ACJ-2Z for pgsql-announce@lists.postgresql.org; Wed, 16 Sep 2026 02:53:08 +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.98.2) (envelope-from ) id 1x6flg-00000000geY-2lKy for pgsql-announce@lists.postgresql.org; Wed, 16 Sep 2026 02:53: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=mxKjmmqC5vtIBcH70WYHnCOJdHcBCAuhMFIrluMvWH0=; b=R+cv++TGCHTt9oKFRILJiX9Icm an12nts8U2khb8PWKxgZ9GQiGp6XeL4hyXW0j5WLkIKcF1jBwKgPzTtKLPi6Q4Z79TIe38pYogySX vgdSaMARpvsqJzopaRaB6gy23V5qdb3R+MNwrNtUe4zLKKfcqBxEORIo9eoR+p9WG8L+GTrDNUSum fLY42NWpC2v1qSgLCyCYf4Wz+svH62IJujIOsuS/ecbU12fGr8es3MWCZBawzX7nC5GkOxsRqTZIG pId3nS67lQohE0UCFqfIwqN6oRmPCy5AkSHMcYZ8ngxfNWUlGqzjnGOx1rTz7P17YBdgPLy9AOvXv zZWF9TTQ==; 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.96) (envelope-from ) id 1x6flg-000pPD-1E for pgsql-announce@lists.postgresql.org; Wed, 16 Sep 2026 02:53:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x6flf-00000004WcA-1Qzd for pgsql-announce@lists.postgresql.org; Wed, 16 Sep 2026 02:53:03 +0000 Content-Type: multipart/alternative; boundary="===============0072992140359581679==" MIME-Version: 1.0 Subject: pgAssistant 3.8.0 : continuous improvement loop for Postgres To: PostgreSQL Announce From: pgAssistant dev team via PostgreSQL Announce Reply-To: hartwig.bertrand@gmail.com Date: Wed, 16 Sep 2026 02:52:59 +0000 Message-ID: <178952717935.1256.3445053158444721743@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 09a02dfdfc2f91ab21473bfac520b62fe8e486d6033736830561c483d19f2f1f List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============0072992140359581679== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable With this release, pgAssistant is evolving beyond PostgreSQL analysis and t= uning to become a **continuous PostgreSQL improvement platform**. The new positioning is built around a **continuous improvement loop**: Observe =E2=86=92 Diagnose =E2=86=92 Prioritize =E2=86=92 Plan =E2=86=92 Im= plement =E2=86=92 Collect again =E2=86=92 Measure pgAssistant already helped identify what should be improved and turn recomm= endations into a prioritized Executive Plan with clear DEV and OPS ownershi= p. Combined with pgAssistant Collector, version 3.8.0 goes further by adding h= istorical 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 detect= ed does not necessarily prove that it was implemented. pgAssistant keeps th= ese distinctions explicit while bringing the relevant evidence together in = one place. pgAssistant is not intended to replace real-time monitoring. Monitoring sho= ws what is happening now; pgAssistant helps teams decide what to improve ne= xt, organize the remediation work, and measure what changed afterwards.