A query uses ORDER BY embedding <-> query_vec LIMIT 10. The table has 1M rows but no vector index. What is the query behaviour?
- A Uses B-tree index automatically
- B Returns an error (no vector index)
- C Performs a full sequential scan computing distance for all rows (correct answer)
- D Uses approximate search with default parameters
Shortcut: Without a vector index, pgvector performs an exact k-NN search via full sequential scan. This provides perfect recall but is slow on large tables. Add IVFFlat or HNSW index for performance.