pgvector
pgvector is an open-source vector extension plugin for PostgreSQL that enables storing, indexing, and querying high-dimensional vector data within a relational database. It supports both exact search and approximate nearest neighbor (ANN) search, provides multiple distance metrics such as Euclidean distance, cosine similarity, and inner product, and is compatible with index algorithms including IVFFlat and HNSW. pgvector is commonly used for storing and retrieving machine learning embedding vectors, allowing developers to implement semantic search and recommendation features within PostgreSQL without a dedicated vector database.
Core Facts
The pgvector extension adds vector storage and similarity search capabilities to PostgreSQL, enabling Supabase to serve simultaneously as a traditional database and a vector database.
Pinecone、Chroma、Weaviate是常见的向量数据库产品
Long-term memory is typically implemented with the help of vector databases (such as Chroma, Pinecone, Weaviate, Milvus, etc.) to enable semantic retrieval.
Timeline (last 90 days)
In pgvector's HNSW index, setting m to 16 and ef_construction to 64 achieves a p99 latency of 12ms under 500 concurrent inserts.
The HNSW index locks the table during batch inserts, causing write stalls of more than 5 seconds; the solution is to write in batches with INSERT ... ON CONFLICT DO NOTHING and a 50ms debounce window.
In pgvector's HNSW index, the parameter m is the number of neighbor edges kept per node, and ef_construction is the size of the candidate queue during construction; together they determine the recall-latency trade-off at query time.
pgvector's default HNSW settings cause insert stalls of more than 2 seconds during batch memory writes.
pgvector's index construction consumes considerable memory, and index maintenance cost under high-concurrency writes rises noticeably with data volume, so load testing should be done against actual data scale and concurrency patterns before production deployment.
If the team is already familiar with PostgreSQL, the marginal cost of introducing pgvector is far lower than standing up a new dedicated vector cluster.
The technical choices for million-scale and billion-scale vectors are completely different: pgvector is often sufficient for the former, while the latter requires careful evaluation of sharding and index rebuild strategies in dedicated engines.
The upsert/delete operations generated by RAG Sync Monitor can be applied directly to vector databases such as Pinecone, Qdrant, Chroma, and pgvector.
CodebaseRAG adopts a hexagonal architecture, where query use cases depend on ports, and pgvector, Qdrant, Ollama and Anthropic sit behind the ports as adapters.
Statewave uses the Apache-2.0 license, depends on Postgres 14+, pgvector, and Python 3.11+, and provides HMAC-SHA256-signed receipts and a replay endpoint that can reconstruct the four properties of an audit trail.
40 more timeline events
All Facts (20)
The pgvector extension adds vector storage and similarity search capabilities to PostgreSQL, enabling Supabase to serve simultaneously as a traditional database and a vector database.
80%VerifiedPinecone、Chroma、Weaviate是常见的向量数据库产品
80%VerifiedLong-term memory is typically implemented with the help of vector databases (such as Chroma, Pinecone, Weaviate, Milvus, etc.) to enable semantic retrieval.
80%Verified典型的RAG流程包括文档切片、向量化嵌入、存入向量数据库、语义检索、上下文拼接和最终生成六个步骤
75%Verifiedpgvector is an open-source extension for PostgreSQL that natively adds vector data types and similarity search capabilities to the relational database, supporting both exact nearest-neighbor and approximate nearest-neighbor (HNSW, IVFFlat index) retrieval modes.
70%VerifiedPinecone is a fully managed, cloud-native vector database.
70%VerifiedPostgreSQL can support vector retrieval via pgvector.
65%Verified向量存储常用专用向量数据库如Pinecone、Chroma、Weaviate，支持近似最近邻检索
65%UnverifiedMaxKB通常集成PostgreSQL的pgvector扩展或独立的向量数据库
75%UnverifiedFor applications with vector scale below tens of millions and insensitivity to latency, pgvector's existing indexes may already be sufficient, and there is no need to introduce new dependencies.
60%UnverifiedMainstream vector databases such as Pinecone, Weaviate, Qdrant, and pgvector generally adopt the HNSW approximate nearest neighbor indexing algorithm at their core.
60%UnverifiedIn pgvector's HNSW index, setting m to 16 and ef_construction to 64 achieves a p99 latency of 12ms under 500 concurrent inserts.
50%Unverifiedpgvector's default HNSW settings cause insert stalls of more than 2 seconds during batch memory writes.
50%UnverifiedThe HNSW index locks the table during batch inserts, causing write stalls of more than 5 seconds; the solution is to write in batches with INSERT ... ON CONFLICT DO NOTHING and a 50ms debounce window.
50%UnverifiedIn pgvector's HNSW index, the parameter m is the number of neighbor edges kept per node, and ef_construction is the size of the candidate queue during construction; together they determine the recall-latency trade-off at query time.
50%Unverifiedpgvector's index construction consumes considerable memory, and index maintenance cost under high-concurrency writes rises noticeably with data volume, so load testing should be done against actual data scale and concurrency patterns before production deployment.
50%UnverifiedThe technical choices for million-scale and billion-scale vectors are completely different: pgvector is often sufficient for the former, while the latter requires careful evaluation of sharding and index rebuild strategies in dedicated engines.
50%UnverifiedIf the team is already familiar with PostgreSQL, the marginal cost of introducing pgvector is far lower than standing up a new dedicated vector cluster.
50%UnverifiedThe upsert/delete operations generated by RAG Sync Monitor can be applied directly to vector databases such as Pinecone, Qdrant, Chroma, and pgvector.
50%UnverifiedCodebaseRAG adopts a hexagonal architecture, where query use cases depend on ports, and pgvector, Qdrant, Ollama and Anthropic sit behind the ports as adapters.
50%