Extended Data Retention for 100 days, Enterprise Server v2026.01.0 & a Thank You from pganalyze
Hi there,
Welcome to 2026! First, I wanted to say thank you to everyone who responded to my email request for product roadmap feedback earlier this week. The amount of replies with thoughtful comments and suggestions was incredibly helpful as we dive into planning for the upcoming year!
As a sign of our gratitude for the support over the years, we'd like to send you a pganalyze swag package. Request one here.
In product news, we're announcing the release of pganalyze Enterprise v2026.01.0 today, which now includes the Query Advisor feature we launched last quarter for Cloud as well as the just announced 100-day retention time for query, table and index statistics. Something many of you have been requesting, and we're excited to deliver!
We're also looking forward to be back in Europe in March where we will have booths at both PGDay Nordic and pgDay Paris. Please reply here if you plan to be at either event, so we can connect.
As always, you can find the complete list of pganalyze product updates, including the Enterprise release details, at the end.
Happy new year,
Lukas
Product News
100 Day Retention Now Available for Enterprise plans
Today, we're excited to announce extended 100 day retention time for query, table and index statistics in pganalyze. In our announcement post you'll get a quick overview on the new feature, and some details on how we made it work behind the scenes, and how our timeseries storage format has evolved over time, and is now utilizing the pco compression library.
If you've been waiting for an Enterprise Server release with the new Query Advisor: The wait is over!
Go head to our release changelog page, learn all the details about the release, you can also find a short summary at the end of this email. Query Advisor, Workbooks in GA, 100 day retention & more!
We also recommend reading about how the migration to the pco-based storage format (that supports the longer retention) may impact your upgrade process, especially when monitoring 100+ database servers with pganalyze.
After upgrading all new EXPLAIN plans coming into pganalyze will be analyzed automatically for Query Advisor - and if we find a problematic query plan pattern, our new alert for bad query plan patterns will tell you right away!
To start 2026, we want to say thank you to the Postgres community that has supported and shaped pganalyze over the years. We are sending out a limited run of pganalyze swag as a small token of appreciation. Depending on availability, this may include stickers, pens, or other pganalyze-branded items.
If you would like one, share your mailing address and we will take care of the rest. Domestic US and international shipping is available, with some country restrictions. Your address will only be used to send this package.
Closing out 2025 at re:Invent & Kicking Off 2026 at PGDay's in Helsinki & Paris
We wrapped up 2025 at AWS re:Invent with a great few days of conversations with Postgres practitioners working on real production challenges. One theme was impossible to miss: AI was everywhere. We had thoughtful discussions about why pganalyze does not rely on AI for its advisors today, especially when it comes to trust, explainability, and actionable insights. At the same time, your feedback has us thinking more deeply about where integrating with AI tooling could genuinely be useful, and we are actively exploring options, including an MCP Server integration.
To kick off the year, we are continuing these conversations to Europe. We will have booths at Nordic PGDay in Helsinki on March 24, 2026, and pgDay Paris on March 26, 2026. If you are attending either event, we would love to connect in person and continue the discussion around Postgres performance, operating in production, and what is coming next.
Show View detail page when a view is loaded through the Table detail page
Logical Date Ranges
Currently, when a period like "Last 24h" is selected in the date picker, this is only resolved to a concrete date range (e.g., "2025-12-04 00:00:00 to 2025-12-05 00:00:00") once.
If you use the app for an extended period of time, that resolved date range is stuck in the past and grows stale.
Instead, re-resolve the date range periodically (only when navigating to a new page) to ensure fresh data is always loaded.
Product Updates
pganalyze Enterprise Release v2026.01.0
Features
Enable 100 day retention for query and schema statistics
pganalyze Enterprise Server now stores 100 days (increased from 30 days) of history for query statistics and table/index statistics.
The date picker interface has been updated to reflect the additional retention time and to allow selecting longer time frames.
Query Advisor: Proactive query plan optimization for Postgres is now generally available
Query Advisor continuously analyzes EXPLAIN plans in the background to detect problematic patterns and provide actionable query rewrites.
Detected issues appear in the Query Advisor landing page, Workbooks, and query detail views.
The Query Tuning Workbooks feature is now generally available (GA), and has been renamed "Workbooks"
Add list of workbooks related to the query in the query details page
Improve SQL editor with syntax highlighting and auto-completion
Support viewing differences between Query Plan variants
Support choosing parameter sets from query samples even if parameters are merged
Fix parameter type inference when IN lists are used
Show "Run EXPLAIN" option on the overview page when upload is incomplete
Move the workbook info sidebar on the Overview page from the left to the right side for better consistency across the app
Add built-in diffing option in Editor When drafting a new Query Tuning variant, you can now compare the diff of that draft against the original query.
Format and normalize query text using standardized SQL format
Further improve internal statistics compression using specialized "pco" format
Combine queries run by multiple Postgres roles
Support showing scans information for the index of the partition parent
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.
