A quick review checklist after creating an index.

Section: What good looks like

Healthy plan signals

text
text
Look for:
- indexed search instead of full scan
- fewer rows/docs examined
- fewer extra sorts
- lower latency under realistic load
- acceptable write overhead
Explanation

Do not stop at 'the index exists'. Confirm that it materially improves the real workload.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Related commands

Same sheet · prioritizing What good looks like
PostgreSQL EXPLAIN ANALYZE
See actual runtime, loops, and buffer reads.
MySQL EXPLAIN
Inspect access path and chosen key.
SQLite EXPLAIN QUERY PLAN
Inspect scans versus indexed searches.
MongoDB executionStats
Check keys examined and docs examined.
OpenIn sheetjavascript