I found the following argument on some of the downsides of pgVector interesting:

The Case Against pgvector | Alex Jacobs
What happens when you try to run pgvector in production and discover all the things the blog posts conveniently forgot to mention

It's worth reading Alex' whole article - it's mostly bullet points and summary paragraphs. It reads like the opposite of our internal engineering design document for C-SPANN, which has been built to address exactly the weaknesses in pgVector that Alex highlights.


Another article, A Practical Guide for Choosing a Vector Database: Considerations and Trade-Offs, seems to have been written by someone with some real-world experience. Again, their cautions line up with what we're trying to accomplish with CockroachDB and C-SPANN.

A Practical Guide for Choosing a Vector Database: Considerations and Trade-Offs | VectorHub by Superlinked
Learn how to choose the right vector database for your AI application based on architecture, not feature lists. Explore key considerations: memory vs disk, managed vs self-hosted, indexing strategies, query patterns, and scaling from prototype to production.

Experience CockroachDB Vector capabilities yourself, for free. Get started on CockroachDB Cloud today:

Try CockroachDB Today
CTA Image

Spin up your first CockroachDB Cloud cluster in minutes. Start with $400 in free credits.

Get Started