This is the 1.0 release of Doltgres.

1.0 means:

1. Forward Storage Compatibility: all 1.x releases will be compatible with no data migrations.
2. Production Performance: Fast enough for your production workloads.
3. Postgres Compatibility: Your Postgres tools, libraries and queries will just work.
4. Stable Version Control Interface: Version control queries you write will work for all 1.x releases.

For more detail, read up on the release here:

https://dolthub.com/blog/2026-08-06-doltgres-1-0/

Merged PRs

doltgresql

• 3031: fix unknown type array input for any expr
• 3030: Fix RANGE window frame panics and bugs Fixes panics and silent mishandling when the frame boundary offset is numeric or an INTERVAL over a DATE/TIMESTAMP column. Depends on: https://github.com/dolthub/go-mysql-server/pull/3665
• 3029: Add fast path for binary CompiledFuncs We can avoid memory allocations if we know the number of arguments we're going to process.
• 3026: Add native ntile(), nth_value(), and cume_dist() window functions New window functions for ntile(), nth_value(), and cume_dist() implemented in the Doltgres layer, matching Postgres's exact return types and semantics.
• 3024: Homogenize RootObject and Collection storage This simplifies root object collections by tying them all to use the same underlying storage, and also fixes a few long-standing issues:
• We were aggressive with cache eviction, meaning collections were often cached for only a single statement, since we didn't have good guarantees that separate statements would properly invalidate a stale cache.
• Simply loading a collection would write a different value into the root, as it went from an "unwritten collection" to an "empty collection", which is a material difference as far as the root is concerned. We tried to mitigate this, but it was a per-collection fix.
• Concurrent branch modifications could cause a session to get into an error loop which we couldn't exit in the session, as we'd never clear the error from the previous statement and we'd resurface that error before we could even do anything
• 3023: Revamped extensions to use emulation This removes the old logic of looking at the locally-installed Postgres instance and directly using those DLLs, and replaces it with emulated versions. So far only uuid-ossp really worked in the previous version, and we're successfully emulating it in Go code now. We can follow this same model and implement the other extensions as well.
• 2986: Create a SequenceTracker for Postgres sequences. This is the Doltgres side of https://github.com/dolthub/dolt/pull/11337 The purpose of this PR is for Doltgres to have the same behavior for sequences and SERIAL columns that Dolt has for AUTO INCREMENT tables. In order to accomplish this, we introduce a SequenceState type that mirrors the AutoIncrementState in Dolt. The GlobalState has trackers for both that manage a state for each Sequence object.

Closed Issues

• 3034: 0.57.3 arm64 Docker image ships the 0.57.2 binary (dolt_version() returns 0.57.2)
• 3042: (withdrawn)
• 2240: support for xmin and other hidden system columns