beta + limitations
DoltGres is in Beta. This page is the calm, honest list of what to expect — so nothing surprises you in production. The team ships fast, so treat this as a snapshot, not a permanent ceiling.
where it is in its life
- Still pre-1.0 Beta; 1.0 is targeted for around October 2026.
- Roughly 5.2× slower than stock Postgres overall today (about 6.3× on reads, 3.6× on writes). DoltHub expects this gap to close well before 1.0.
- About 91% correctness on the sqllogictest suite.
- The biggest open issue is general Postgres compatibility: there are still many unresolved
.pgdumpimport failures, so importing an existing Postgres dump may not work cleanly yet.
not yet supported
The following are known gaps at Beta. (For the type system specifically — including the SERIAL gap — see types + sql support.)
| area | status |
|---|---|
| Git-style CLI | version control is driven through the SQL interface only — no separate command-line tool yet |
| push to DoltHub / DoltLab | only custom remotes work today (filesystem and S3) |
| backup & replication | both are works in progress |
| GSSAPI auth | not supported |
| statement-level triggers | row-level triggers work; statement-level do not |
| stored procedures | partial — described as "almost done" as of October 2025, not yet complete |
| window functions | not supported yet (verified: row_number() OVER (...) errors on a live instance) |
| custom operators / indexing / aggregates | not supported at Beta |
| multi-table single-statement UPDATE | updating several tables in one UPDATE is not supported |
| ALTER SEQUENCE / COMMENT ON | these DDL statements are not yet supported |
| collations | currently ignored |
| some psql backslash commands | e.g. \d <table> is not supported |
verified working (live probe)
Confirmed against a live DoltGres instance (so you don't have to take an old changelog on faith):
- Common table expressions (
WITH … SELECT) work — includingUNION ALLinside the CTE. current_setting(...)reads work; the default transaction isolation is read committed.- The engine reports itself as PostgreSQL 15.5 over the wire, and the
dolt.version-control system tables (e.g.dolt.branches) resolve.
What Beta IS good for.You can build and evaluate real solutions on DoltGres today — DoltHub explicitly frames Beta as "you can begin building a production solution." The headline superpowers already work: branch, merge, fork, clone, diff, and time-travel over your data, all versioned the way Git versions code. If those are why you're here, they're here now. Just keep this page's gaps in mind, pin to a known-good version, and expect the rough edges to keep getting smoother.