Welcome to the July 2025 edition of the pganalyze newsletter!
If you missed our recent live session, the recording of our Query Advisor webinar is now available. It’s a deep dive into how the new Query Advisor helps detect and fix slow queries. Interested to try it out? We're starting early access for select cloud-based customers next week. Reply to this email if you're interested.
To prepare for the Query Advisor, we are also making a related change: "Query Tuning Workbooks" has been renamed to "Workbooks" in the app and documentation. The functionality hasn’t changed, but this makes the navigation clearer and leaves room for future functionality like testing indexes. If you want to stay up to date with changes, small and large, we now have a changelog available in-app with the What's New link in pganalyze.
New to pganalyze, or not using pganalyze yet? We're now offering dedicatedPostgres Performance Workshops for teams that want hands-on help tuning their own workload. These private sessions are designed to help you get started with pganalyze and resolve your particular Postgres performance challenges. Reach out if you would like to request one for your team.
On the community side, we're launching our new pg_stat_plans extension at the Postgres for All virtual meetup on Sept. 11th. And in November, Ryan and I will be leading a pre-conference workshop at PASS Summit on how to port yourSQL Server tuning skills to Postgres. We’d love to see you there!
As always, check out our product updates and full list of upcoming events at the end of this email.
All the best,
Lukas
Webinar Recording: Detect and Fix Slow Postgres Queries with pganalyze Query Advisor
Missed the live session? You can now watch the recording on demand to see how Query Advisor, a purpose-built query optimization workflow coming soon to pganalyze, helps detect and fix slow Postgres queries using your real query plans.
We walk through how it works, share real-world examples (including a 1000x improvement), and demo how you can confidently rewrite queries with side-by-side plan comparisons in pganalyze Workbooks. You can reply to this email if you haven't already expressed interest in the early access program, which starts next week for cloud customers.
Postgres Performance Workshops for Teams New to pganalyze
We’re now offering dedicated Postgres Performance Workshops to help engineering teams confidently tune their own database. In this hands-on session, you’ll learn how to:
Rewrite slow queries with actionable guidance
Minimize indexing overhead
Set up alerting and maintenance workflows for production
Workshops are open to those with a significant Postgres footprint and new to pganalyze. Availability may book up fast, so request your spot today.
Brush Up on Query Tuning Fundamentals with Lukas' Talk from Posette
Watch this 20-minute talk, where Lukas shares what he’s learned tuning slow Postgres queries over the years. You’ll get a quick refresher on EXPLAIN ANALYZE, then dive into his iterative process for identifying the root cause of slowness, including common planner pitfalls and how to evaluate alternate plans with tools like pg_hint_plan.
We’re excited to be participating in several Postgres community events throughout 2025! Ryan's talk is coming up quickly at PGDay Austria, the new pg_stat_plan extension is being featured at the Postgres for All virtual meetup on Sept. 11th. And in November, Lukas & Ryan will be leading a pre-conference workshop at PASS Summit on how to port your SQL Server tuning skills to Postgres. Hope to see you there!
EXPLAIN Plans: Added support to show the extra information (like the execution time) when JSON format view is selected
Previously, when the JSON format view is selected, it was dropping the information like "Planning Time", "Execution Time", "Query Identifier", etc.
With this change, the JSON format view will show all information captured with the auto_explain.
If the auto_explain is using a text format, it's converted to the JSON format with best effort.
Schema Statistics: Add support for handling named NOT NULL constraints, added in Postgres 18
When running the upcoming Postgres 18 release, you will see columns marked as NOT NULL on each table's "Columns" tab, as well as the automatically created named NOT NULL constraints on the "Constraints" tab.
Workbooks
As part of the beta testing process, and looking ahead for future navigation changes with the upcoming Query Advisor, we are dropping the "Query Tuning" prefix from Workbooks for clarity.
The previous menu item "Query Tuning" has now been renamed to "Workbooks".
We are also making this change to support future use cases for pganalyze Workbooks that may not involve query tuning directly, for example testing index changes, etc.
Bug Fixes & Other Improvements
Fix page focus after loading to allow scrolling the main content with arrow keys
Add a "What's New" menu item that shows a list of recent user-visible changes to pganalyze.
Add Inter as a fallback font option for the application UI
Optionally support PostGIS in Index Advisor for Enterprise Server deployments
Due to PostGIS licensing restrictions, PostGIS is not bundled with pganalyze Enterprise Server, but this release now allows adding in the required files to a custom image
Reach out to us via a support ticket for details
Update bundled collector from 0.65.0 to 0.66.2
Note that some of the new functionality (e.g. pg_stat_io tracking) is not yet enabled in this Enterprise Server release, as this update is mainly aimed to pull in collector-side bugfixes.
Enforce correct search_path for internal corrections
This ensures the partition creation changes in 2025.03.3 do not cause problems on systems where a "pganalyze" user is used, and a "pganalyze" schema is present
Resolves errors like "no partition of relation ... found for row" that caused missing data in some cases
Immediately create internal table partitions on boot
Log details when there are partition creation problems
Dependency security updates and other routine security updates to packages in the base image