Postgres Index Recommender

Paste the output of EXPLAIN ANALYZE. Get back the most likely missing indexes, ordered by impact. Heuristic. Verify the suggestion against your actual data distribution before shipping.

EXPLAIN ANALYZE output

1 finding

HIGHorders

Sequential scan filtering 1,248,321 rows. Add an index on the filter columns.

Index status, created_at together (multi-column index) if both are always filtered, otherwise index the highest-cardinality column first.

CREATE INDEX CONCURRENTLY idx_orders_status_created_at
  ON orders (status, created_at);

Reminders: always use CREATE INDEX CONCURRENTLY in production. Confirm column cardinality before adding indexes (low-cardinality boolean indexes usually make things worse). Run EXPLAIN ANALYZE again post-deployment to confirm.

85 of 86 run entirely in your browser (Weather Widget uses Open-Meteo).

·Share on X Share on LinkedIn

Saved you time? Buy me a coffee