Shipped · Databases

What yugabyte/yugabyte-db shipped

The public repository of Yugabyte · github.com/yugabyte/yugabyte-db

Written by FoxPlug from the repository's own releases; not affiliated with Yugabyte. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/yugabyte/yugabyte-db; Yugabyte did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

Follow yugabyte-db's weekly shipped digest

Week of October 5, 2026

What shipped

Why it matters

This week cuts cluster startup latency across the board: quicker master leader election, initdb overlapping the wait for the master, an immediate first YSQL lease, and fewer postgres starts per node. It also trims client-side and tserver-side overhead, undoes a heartbeat deadlock, returns freed preload memory to the OS, and exposes standard PostgreSQL auto analyze columns so monitoring works with familiar views.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Cluster startup gets faster this week: quick master leader election, tserver initdb overlapping the wait for master, an immediate first YSQL lease, and fewer postgres starts per node. Plus fewer postgres starts, heartbeats deadlock fix, and last_autoanalyze in pg_stat_user_tables

Post for LinkedIn

This week's changes focus on how fast a cluster and its connections come up. yb-master now defaults quick_leader_election on, so an RF3 universe does not wait a full election timeout for its first master leader on create or restart. The tserver runs its local initdb while waiting for the master rather than after TabletServer::Init, skips config probes and the postgres version check during local initdb, and requests its first YSQL lease immediately instead of waiting a full refresh interval. Tests shut down ExternalMiniCluster tablet servers in parallel. Elsewhere: retryable request ids come from sharded lock free allocators, strings::Substitute and StringPrintf are replaced by Format() in src/yb, free memory is returned to the OS after connection startup, a heartbeat deadlock with colocate

Week of September 28, 2026

What shipped

Why it matters

This week's changes focus on reducing memory overhead in catalog operations and improving observability for cache and SST behavior. Memory improvements to catalog preload and relcache building will reduce connection latency and peak memory on first connections after DDL. New cache metrics and SST statistics exports enable operators to build dashboards and understand compaction thresholds.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Catalog preload now frees memory per row instead of batching, and cache metrics update outside locks. SST statistics export to Prometheus for monitoring.

Post for LinkedIn

This week we reduced catalog preload memory overhead by freeing scanned rows immediately rather than batching deletions, lowering peak memory during first connections after DDL. Cache statistics now update outside mutex locks to reduce contention. We also added Prometheus exports for SST garbage statistics, enabling operators to build dashboards and study compaction thresholds.

Week of September 21, 2026

What shipped

Why it matters

This week ships improvements to query performance and reliability: catalog preloading is faster on large clusters, placement constraints provide better control over replica distribution, and thin client support for more column types enables new use cases. Several fixes address crashes, deadlocks, and test isolation issues that improve stability.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

New in yugabyte-db: faster DDL on large catalogs with adaptive response budgets, placement block replica limits, thin client UINT32 support, reduced lock contention in operation tracking, and per-drive fsync metrics.

Post for LinkedIn

This week's yugabyte-db updates focus on performance and reliability improvements. Catalog preloading now adapts to response size budgets instead of fixed row limits, reducing latency after DDL on large clusters. New placement block constraints give operators fine-grained control over replica distribution. The thin client gains support for UINT32 columns to open tables keyed by oids. Lock contention improvements reduce blocking in operation tracking. Per-drive write throughput metrics alongside fsync latency provide clearer device performance visibility.

Week of September 14, 2026

What shipped

Why it matters

Distributed tracing infrastructure across RPC boundaries and thread hops enables operators to track requests through the entire system. Improvements to error reporting, resource limits, and safety checks make the database more reliable and easier to debug.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Distributed tracing now flows across RPC boundaries, thread hops, and shared memory exchanges. Better error codes and safety checks improve debugging and prevent silent failures.

Post for LinkedIn

This week's work strengthens distributed tracing throughout YugabyteDB. Trace context now propagates across RPC boundaries, thread boundaries, and the PG-tserver shared memory path—enabling operators to follow requests through the entire system. We also improved error reporting with proper PostgreSQL error codes, added resource limits for xCluster operations, and added safety checks to fail fast when critical components are missing.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-13.

Is this your repo? Ask us to remove this page.