Skip to content

dolt

v2.0.3 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 20d Relational Databases
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

agent-memory agent-memory-server ai-agents ai-database data-version-control data-versioning
+14 more
database database-version-control database-versioning decentralized-database git git-database git-for-data git-for-databases git-sql immutable-database mariadb mysql sql version-controlled-database

Summary

AI summary

Fixes PID leak by removing remote DB cache and closing databases after each use.

Changes in this release

Feature Medium

Autogc load scheduler now independent of number of CPUs.

Autogc load scheduler now independent of number of CPUs.

Source: llm_adapter@2026-05-21

Confidence: low

Dependency Medium

`decimal.Decimal` replaced with `*apd.Decimal` across dolt and go-mysql-server.

`decimal.Decimal` replaced with `*apd.Decimal` across dolt and go-mysql-server.

Source: llm_adapter@2026-05-21

Confidence: low

Bugfix Medium

SSH subprocesses created by sql-server instances now close properly, preventing PID leaks.

SSH subprocesses created by sql-server instances now close properly, preventing PID leaks.

Source: llm_adapter@2026-05-21

Confidence: high

Bugfix Medium

Bug fix for dropping sort nodes in go-mysql-server.

Bug fix for dropping sort nodes in go-mysql-server.

Source: llm_adapter@2026-05-21

Confidence: low

Full changelog

Merged PRs

dolt

  • 11028: drop remote db cache, Close() after each use
    SSH subprocesses created by sql-server instances were failing to clean up because the Close() method was never being called. This was the result of some caching done by GetRemoteDB in the sqle package. Most of this change is to remove sqle.DoltDatabaseProvider.GetRemoteDB() caching, allowing for push/pull operations to safely Close() remote databases after use. Thus, preventing the PID leak in the associated issue (#10897)
    Git remote database singletons are a special case. Previously the push operation only would cache these instances - which are expensive to create initially since they need to perform git operations to get in sync with the remote. There is no reason go Close() them though, so we keep a singleton for the duration of the sql-server process.
    Fixes: https://github.com/dolthub/dolt/issues/10897
  • 10990: replace all decimal.Decimal with *apd.Decimal
    Depends on https://github.com/dolthub/go-mysql-server/pull/3532
  • 10953: fix autogc load scheduler to be independent on number of CPUs
    Before, we had a threshold that was incorrectly calculating the threshold based off the number of CPUs.
    The original intention is to prevent AutoGC if a single CPU core exceeds 50% usage.
    We've determined that CPU Load itself is not a great metric to schedule AutoGC, but this is a fix for now.
    addresses: https://github.com/dolthub/dolt/issues/10944

go-mysql-server

  • 3539: Bug fix for dropping sort nodes
    Also fixed a couple under-specified goup concat tests.
    The latter were relying on a particular row storage order which is not guaranteed and broke when Dolt changed some encoding parameters.
  • 3532: replace all decimal.Decimal with *apd.Decimal

Closed Issues

  • 10944: Auto-GC never fires on multi-core systems: loadAvgGCScheduler threshold formula is inverted
  • 9248: support returning clause in inserts like mariadb ?
  • 10897: dolt sql-server leaks one ssh child process per CALL dolt_fetch against an ssh:// remote

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track dolt

Get notified when new releases ship.

Sign up free

About dolt

Dolt – Git for Data

All releases →

Related context

Earlier breaking changes

  • v2.0.4 `DOLT_CHECKOUT('<table>')` now gated with Write permission.

Beta — feedback welcome: [email protected]