cevian

@ceviantech.bsky.social

Tech lead for pgai, pgvectorscale, and all other AI things @ Timescale. Postgres rocks!

I’ve been thinking about why LLMs are bad at text-to-sql. Short answer: no context 🧵 Compared to developers, LLMs are more handicapped without context: - They can’t read the application code. - They can’t ask around. - They don’t know where the docs are.

🚫 Stop treating embedding generation like ETL. ✅ It’s indexing. One of the most common misconceptions in the world of AI and LLMs: 👉 Vector embedding generation = ETL. Nope. It’s much more like building an index. Conceptually, it's just like creating a full-text index on your data.

Listening to our CTO Michael Freedman talk about the evolution from data lakes (unstructured) and data warehouses (structured) into unified data lakehouses, I had a thought...

𝗦𝗜𝗠𝗣𝗟𝗜𝗙𝗬 𝗗𝗢𝗖𝗨𝗠𝗘𝗡𝗧 𝗘𝗠𝗕𝗘𝗗𝗗𝗜𝗡𝗚𝗦 𝗪𝗜𝗧𝗛 𝗣𝗚𝗔𝗜 𝗩𝗘𝗖𝗧𝗢𝗥𝗜𝗭𝗘𝗥: 𝗣𝗼𝘀𝘁𝗴𝗿𝗲𝘀 + 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 We've expanded pgai Vectorizer to automatically create searchable vector embeddings in Postgres from documents stored in S3 while keeping the original files in place.

Vectorizer architecture and code snippet

We just released a new database analytics benchmark. RTABench is geared to talking about real-time analytic /applications/ (that is how it differs from ClickBench).

Vasily Grossman's "The Road" (the story, somewhat confusingly published in "The Road" collection of essays) may be the single best description of depression I've ever seen in writing. Incredibly, it's told from the vantage point of a Mule!

Testing out a theory about Math education: Can you explain why a times b = b times a (a*b=b*a)? If so, what's you explanation? If not, I'd also like to know!

AI doom scenarios often feel a bit off to me—not because they're wrong about AI being risky, but because they imagine the danger as some AGI-built Terminator rising up to enslave humanity. Honestly, the real risks seem a lot more... human.

The "easy mode" open source AI stack