Production vector workloads rarely involve unfiltered nearest-neighbor searches, requiring hybrid patterns that combine semantic similarity with scalar filters. While pgvector uses HNSW indexes for approximate nearest neighbor acceleration, adding WHERE clauses introduces complexity and requires careful tuning. The iterative index scans used for filtered search involve specific tradeoffs that impact query performance and planning.
- Real-world vector queries usually require hybrid search combining similarity scores with scalar filters.
- pgvector's HNSW indexes accelerate ANN queries but need tuning when combined with WHERE clauses.
- Iterative index scans are used for filtered search but introduce specific performance tradeoffs.
- Simple nearest-neighbor patterns are rare; most use cases need filtered vector retrieval.