Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/PostgreSQL
PostgreSQLmedium

When should you use a composite index?

Tags
#composite-index#query-planner#performance
Back to categoryPractice quiz

Answer

Use a composite (multi‑column) index when queries commonly filter or sort by the same set of columns in the same order. PostgreSQL uses the leftmost‑prefix rule, so column order matters. Avoid composites if leading columns are low‑selectivity or rarely used together.

Related questions

PostgreSQL
Materialized view vs view: what’s the difference?
#postgres#views#materialized-view
PostgreSQL
PostgreSQL bloat: what causes it and how do you reduce it?
#postgres#mvcc#vacuum
PostgreSQL
PostgreSQL `COPY`: what is it used for and why is it fast?
#postgres#copy#bulk-load
PostgreSQL
What is a partial index in PostgreSQL and when is it useful?
#postgres#index#partial-index
PostgreSQL
What is `work_mem` and why can sorts or hash joins spill to disk?
#work_mem#sort#hash-join
PostgreSQL
BRIN vs B-tree index — when is BRIN a good fit?
#brin#btree#index