The author shares hands‑on experiences with Milvus, pgvector, and Qdrant, detailing performance at different data scales, index trade‑offs, operational complexity, and provides practical guidance on selecting the most suitable vector database for a RAG system.
An interview story reveals that storing embeddings in MySQL forces a full‑table scan, leading to second‑level latency, while production‑grade RAG requires a vector database with ANN indexing such as HNSW or IVFFLAT, offering millisecond response, high recall, and scalable storage.
This article introduces xi‑ops, an open‑source AI assistant that lets users query data and troubleshoot incidents with natural language while enforcing strict execution rights and key management, and details its architecture, security principles, deployment model, and first‑phase feature set.
PostgreSQL is attracting renewed interest not because it magically becomes an all‑purpose AI database, but because AI applications in production demand a unified, consistent platform that can manage business records, vector embeddings, agent state, permissions and tooling, and PostgreSQL’s extensible ecosystem—pgvector, serverless architectures, branching, and MCP—offers exactly that blend of relational reliability and AI‑native capabilities.
This article walks Java developers through turning Spring AI into an enterprise‑grade AI agent that can query internal databases, access a vector‑based knowledge base, enforce role‑based permissions, persist chat sessions in Redis, add full observability, and be container‑deployed with Docker and Kubernetes.
The article explains why RAG systems cannot rely on MySQL for embedding storage, shows the O(n) brute‑force search latency for hundreds of thousands of chunks, and demonstrates how vector databases with ANN indexes such as HNSW or IVFFLAT provide millisecond‑level response, high recall, and scalable storage.
An end‑to‑end multi‑agent Retrieval‑Augmented Generation platform is presented, featuring compositional reasoning, systematic multi‑dimensional evaluation, and a controlled prompt‑improvement loop that automatically identifies weak prompt dimensions, proposes diffs, and requires human approval before deployment, with full observability via SSE and persisted logs.
The article questions whether dedicated vector databases are truly needed for AI applications, examining market hype, the rapid emergence of many vector‑DB products, real‑world examples like PostgreSQL pgvector and major vendor integrations, and the hidden costs of data fragmentation and operational complexity.
PostgreSQL’s extensible architecture lets it evolve from a relational DB into a true multi‑model system supporting graphs, vectors, full‑text, time‑series, GIS and key‑value data, with detailed architecture explanations, practical code demos, cross‑model queries, extension selection, and production‑grade best‑practice tips.
GBrain, an open‑source AI memory hub created by YC partner Garry Tan, combines Postgres tsvector keyword search with pgvector semantic search via RRF, manages thousands of Markdown notes, and runs an automated nightly agent that refines and links memories, offering a practical long‑term recall layer for agents like OpenClaw and Hermes.
This comprehensive guide explains how to design, implement, and operate a production‑ready Retrieval‑Augmented Generation (RAG) platform using Spring AI and PostgreSQL PGVector, covering architecture, indexing, hybrid retrieval, prompt engineering, scaling, security, observability, deployment, and common pitfalls for enterprise knowledge‑base applications.
This guide explains why pure vector retrieval often fails for version‑specific queries, introduces hybrid search that combines semantic and keyword matching, and provides step‑by‑step code and SQL examples for enabling PgVector hybrid search in LangChain4j 1.11.0.
The article examines how PostgreSQL’s latest pgvector 0.8.0 release adds iterative index scans and smart query planning, enabling fully free vector search within an existing relational database, compares performance, cost, and architecture against dedicated vector databases like Pinecone, and outlines migration steps and best‑practice guidelines.
This article explains the need for vector databases in the AI era, reviews PostgreSQL's extensible ecosystem, compares vector‑database options, provides step‑by‑step PgVector installation and usage, shares operational best practices, performance tuning tips, and real‑world Qunar & Tujia case studies.
This article explains the necessity of vector databases for AI workloads, reviews the PostgreSQL ecosystem, compares vector database options, provides detailed PgVector installation and usage steps, shares operational best‑practices, performance tuning tips, and real‑world deployment cases at Qunar and Tujia.
