PostgreSQL index decision guide
Why might PostgreSQL ignore my proposed index?
Test whether PostgreSQL selects a proposed index for representative query shapes before creating it.
The problem
A proposed index looks useful, but PostgreSQL may still prefer a sequential scan.
How IndexPilot helps
IndexPilot can create a session-local HypoPG index and ask PostgreSQL whether representative workload shapes select it. It does not diagnose whether an existing production index is safe to keep or drop, and planner evidence is not a latency guarantee.
Try it
$ pipx install indexpilot
$ indexpilot review --candidate-file proposed-index.sql --hypopg
$ indexpilot review --candidate-file proposed-index.sql --hypopg
- Planner selected the exact hypothetical shape
- Estimated planner-cost change
- Inconclusive result when evidence is insufficient
Important limit
IndexPilot decides whether an index has enough evidence to benchmark. It does not claim that planner cost equals production latency or that an index is safe to ship.