doltgresql

You asked for it, we built it: the world's first version-controlled SQL database, Dolt, now has a Postgres-compatible version, Doltgres. We announced the limited alpha here on Hacker News 18 months ago, and today we're excited to announce the Beta release. Doltgres is free and open source, and you can download it from our GitHub repository here: https://github.com/dolthub/doltgresql/ More details on the Beta release in our announcement blog post: https://www.dolthub.com/blog/2025-04-16-doltgres-goes-beta/ If you've been waiting for the Postgres version of Dolt, wait no more. Please give it a try by importing your Postgres database using pg_dump and psql, then playing around with the version control features. Let us know via GitHub issues if you encounter any problems. This release represents 18 months of engineering and innovation. We're

PostgreSQL support here https://github.com/dolthub/doltgresql Background and architecture discussion here https://dolthub.com/blog/2023-11-01-announcing-doltgresql/

> Why is Dolt MySQL flavored? TLDR; Because go-mysql-server existed. https://www.dolthub.com/blog/2022-03-28-have-postgres-want-d... We have a Postgres version of Dolt in the works called Doltgres. https://github.com/dolthub/doltgresql We might have a go-postgres-server package factored out eventually.

We're writing a postgres-compatible database that doesn't use any postgres code: https://github.com/dolthub/doltgresql/ We're doing this because our main product (Dolt) is MySQL-compatible, but a lot of people prefer postgres. Like, they really strongly prefer postgres. When figuring out how to support them, we basically had three options: 1) Foreign data wrapper. This doesn't work well because you can't use non-native stored procedure calls, which are used heavily throughout our product (e.g. CALL DOLT_COMMIT('-m', 'changes'), CALL DOLT_BRANCH('newBranch')). We would have had to invent a new UX surface area for the product just to support Postgres. 2) Fork postgres, write our own storage layer and parser extensions, etc. Definitely doable, but it would mean porting our existing Go codebase to C, and not being able to share code with Dolt

Very cool. I wonder when it makes sense to engineer things at this level vs using something like Azure AI search. [0] Love to see version control on all the things! Wonder if the version control features would be more robust if implemented in Doltgres. [0] https://azure.microsoft.com/en-us/products/ai-services/ai-se... [1] https://github.com/dolthub/doltgresql

From the company behind Dolt—the world's first fully versioned database—comes DoltgreSQL, which implements PostgreSQL's variant of SQL. DoltgreSQL is at a very early stage, and we have quite a lot of work left to do, but we'd love to hear all thoughts and opinions! You can read more in the announcement blog post: https://www.dolthub.com/blog/2023-11-01-announcing-doltgresq...