4 ms·
Postgres for agents, of course! It makes too much sense.
by thr0w 1y ago
Postgres for agents, of course! It makes too much sense.
- jacobsenscott 1y agoThe agent stuff is BS for the pointy hairs. This seems to address real problems I've had with PG though.
- akulkarni 1y agoYeah, I know what you mean. I used to roll my eyes every time someone said “agentic,” too. But after using Claude Code myself, and seeing how our best engineers build with it, I changed my mind. Agents aren’t hype, they’re genuinely useful, make us more productive, and honestly, fun to work with. I’ve learned to approach this with curiosity rather than skepticism.
- akulkarni 1y agoThanks! We agree :-) We just launched a bunch around “Postgres for Agents” [0]: forkable databases, an MCP server for Postgres (with semantic + full-text search over the PG docs), a new BM25 text search extension (pg_textsearch), pgvectorscale updates, and a free tier. [0] https://www.tigerdata.com/blog/postgres-for-agents https://www.tigerdata.com/blog/postgres-for-agents
- xpe 1y agoHard to say if the above comment is serious or sarcastic. To my eye, seeing "Agentic Postgres" at the top of the page, in yellow, is not persuasive; it comes across as bandwagony. (About me: I try to be open but critical about new tech developments; I try out various agentic tooling often.). But I'm not dismissing the product. I'm just saying this part is what I found persuasive: > Agents spin up environments, test code, and evolve systems continuously. They need storage that can do the same: forking, scaling, and provisioning instantly, without manual work or waste. That explains it clearly in my opinion. * Seems to me, there are taglines that only work after someone in "on-board". I think "Agentic Postgres" is that kind of tagline. I don't have a better suggestion in mind at the moment, though, sorry.