Gnomon. Git for Postgres data, built for agents
shawkisukkar
22 points
11 comments
November 13, 2026
Related Discussions
Found 5 related stories in 143.0ms across 12,728 title embeddings via pgvector HNSW
- Pgbot: A 5.9 MB read-only Postgres tool for humans and agents sashash · 47 pts · August 25, 2026 · 63% similar
- The Git Forge for Agent-Human Collaboration lizziepika · 55 pts · October 26, 2026 · 53% similar
- The bridge to agent-scale Git infrastructure Klaster_1 · 59 pts · October 21, 2026 · 53% similar
- Neki – Sharded Postgres simon_weber · 223 pts · September 10, 2026 · 52% similar
- DuckPGQ – A DuckDB community extension for graph workloads rzk · 49 pts · July 24, 2026 · 51% similar
Discussion Highlights (7 comments)
xyzsparetimexyz
Gnomore of this please
bedstefar
Is anyone using this?
ulrikrasmussen
I'm fine with people using LLMs to generate code, but I am so, so tired of reading README.md files written by AI. If you want me to take any interest in your idea, please spend the hour or two it takes to explain what you did (or made your agent do) and why, using your own words. LLMs will make anything sound like a good idea on the surface, and I as a reader have to dig in and spend mental capacity to separate the fluff from what is actually a good idea. I'm not going to do that, I'm just going to close the tab. What I want to read in the README.md is an actual human expressing an actual need and an actual idea for how to address it. Sure, use an LLM to get feedback on your writing, maybe even let it help you develop good examples. But if you can't even write a single coherent sentence on your own, keep your project to yourself and stop wasting the time and attention of others.
nepthar
I wonder if the prompt was "Make a HN front page project complete with post, docs, repo, and tutorial. Make it seem like it's been around for a while. Pick two popular concepts and go with it"
sp4cec0wb0y
> Gnomon is a PostgreSQL extension that gives your database branches, history, merges and undo. Give an agent its own branch of your real database, as nothing more than a connection string. See every field it changed, merge it into main when it's right, and undo it if it wasn't. I don't know if I like the idea of handing an agent direct access to db migrations when db migrations already exist through code in most applications (which are then managed by git). What would the use case be for this that isn't already handled through migration code in git?
alexpadula
The idea is cool but the execution needs work. Lot's of holes in technical detail currently. Keep working on it!
horsawlarway
Look functionally very similar to doltgres...? https://github.com/dolthub/doltgresql