Skip to content

Commit 39e6b85

Browse files
bosconiclaude
andcommitted
v26.49.1 release notes (final)
v26.49.0 ships to Cloud on 2026-11-05, and v26.49.1 ships to Self-Managed on 2026-11-06. - Retitle the section v26.49.1 and mark its Cloud date as v26.49.0. - Add the Console's Hydration tab and the Freshness page on Self-Managed to Improvements, and the clusters list's swap-in-Disk fix to Bug Fixes. - Point the operator compatibility row at v26.49.1 and its #v26491 anchor. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent e4f5e02 commit 39e6b85

2 files changed

Lines changed: 9 additions & 6 deletions

File tree

‎doc/user/content/releases/_index.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,13 @@ Starting with the v26.1.0 release, Materialize releases on a weekly schedule for
2020
both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for details.
2121
{{</ note >}}
2222

23-
## v26.49.0
24-
*Released to Materialize Cloud: 2026-11-05* <br>
23+
## v26.49.1
24+
*Released to Materialize Cloud: 2026-11-05 (v26.49.0)* <br>
2525
*Released to Materialize Self-Managed: 2026-11-06* <br>
2626

2727
### Improvements {#v26.49-improvements}
28+
- **Investigate hydration on the cluster details page**: The Console's [redesigned cluster details page](#v26.47-cluster-details-page) gains a **Hydration** tab that charts each replica's hydrations over the last 24 hours, 7 days, or 30 days with their duration, peak memory, disk, and heap use and the objects that took longest, shows which objects a hydrating replica is working on, and calls out a replica that keeps restarting without finishing, such as one running out of memory.
29+
- **Freshness page on Self-Managed**: The Console's [Freshness page](#v26.48-freshness-page), which tracks p90, p99, p99.9, and maximum freshness across your environment's objects, is now available on Materialize Self-Managed.
2830
- **Manage auto-scaling policies in the Console**: The Console's Alter cluster form can now set, change, or remove a managed cluster's [auto-scaling policy](/clusters/autoscaling/), including its hydration size and linger duration, and the opt-in [redesigned cluster details page](#v26.47-cluster-details-page) gains a configuration drawer that shows a cluster's settings, replicas, and auto-scaling policy.
2931
- **Higher throughput for queries at high concurrency**: In benchmarks of strict serializable single-row indexed queries over 256 connections, skipping unneeded cleanup at commit, completing already-ready reads without an extra queueing step, and lower per-query tracing overhead together raised throughput by 63-67%, smaller per-query allocations raised it by a further 26-30% over that build, and prepared queries over 512 connections reached 47% higher throughput in a single benchmark run by no longer registering a timeout timer when network I/O completes immediately.
3032
- **`DROP INDEX` no longer orphans the objects reading from an index**: `DROP INDEX`, with or without `CASCADE`, now fails with an error that names the dependent objects when a materialized view or another index reads from the index, instead of leaving those readers running on an orphaned dataflow, so drop the readers first and drop indexes on the same relation newest first; Terraform configurations that replace such an index need `lifecycle { replace_triggered_by = [...] }` on the materialized view that reads it.
@@ -44,6 +46,7 @@ both Cloud and Self-Managed. See [Release schedule](/releases/schedule) for deta
4446
- **mz-docs**: The skill now finds pages through the live documentation's `llms.txt` index and fetches them from materialize.com instead of bundling a copy of the docs, so it reads the current documentation and needs network access to materialize.com.
4547

4648
### Bug Fixes {#v26.49-bug-fixes}
49+
- Fixed the Console's clusters list showing a dash in the Disk column for every replica in Self-Managed deployments that use swap, which now shows swap use as a share of the replica's heap limit.
4750
- Fixed `CASE` expressions with many or deeply nested arms overflowing the stack when creating a view, using excessive memory, or taking time exponential in the nesting depth when the branches contain subqueries; creating one large machine-generated materialized view now raises memory use by 1.2 GiB instead of 3.8 GiB.
4851
- Fixed saving the Console's Alter cluster form during a graceful resize or while a burst replica was running, which could cancel the resize even when only renaming the cluster, or keep the extra replicas of the resize or the burst replica.
4952
- Fixed `SELECT DISTINCT` and `GROUP BY` returning duplicate rows on a view or materialized view column computed from a keyed column by a cast that rounds or truncates sub-microsecond `time`, `timestamp`, or `timestamptz` values.

‎doc/user/data/self_managed/self_managed_operator_compatibility.yml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ columns:
55
- column: Release date
66
- column: Notes
77
rows:
8-
- Materialize Operator: v26.49
9-
orchestratord version: v26.49
10-
environmentd version: v26.49
8+
- Materialize Operator: v26.49.1
9+
orchestratord version: v26.49.1
10+
environmentd version: v26.49.1
1111
Release date: "2026-11-06"
12-
Notes: "See [v26.49 release notes](/releases/#v26490)"
12+
Notes: "See [v26.49.1 release notes](/releases/#v26491)"
1313
- Materialize Operator: v26.48.2
1414
orchestratord version: v26.48.2
1515
environmentd version: v26.48.2

0 commit comments

Comments
 (0)