What problem does it solve? Setting up vector similarity search in PostgreSQL involves many tuning decisions—index type, distance operator, storage type, and recall parameters—and wrong choices lead to slow queries, poor recall, or out-of-memory failures. This Skill provides proven defaults and tuning guidance for pgvector so searches stay fast and accurate at scale. ## Core Features & Use Cases - Index Configuration: Set up HNSW indexes with tuned m, ef_construction, and ef_search parameters, plus guidance on when IVFFlat is appropriate. - Storage Optimization: Use halfvec for 50% smaller storage and binary quantization with re-ranking for datasets exceeding 10M vectors. - Filtered Search: Apply iterative scan, partial indexes, B-tree prefiltering, or partitioning strategies for selective WHERE clauses. - Use Case: You are building a RAG application that stores product embeddings in PostgreSQL. Use this Skill to create the table and HNSW index, write the similarity query with proper casts, and tune ef_search until recall meets your target. ## Quick Start Set up a pgvector HNSW index and cosine similarity query for my embeddings table in PostgreSQL.