Explain index design.
01
01
Understand the problem
indexingdatabase
02
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Stuck? AI Nudge Available
Get a conceptual hint to guide your logic without spoiling the final implementation.
03
03
Study the solution
The solution is waiting
Give it an honest attempt first — then compare your thinking with the full walkthrough.
04
04
Read the code
Composite, covering, and partial indexes
-- Composite: serves WHERE (tenant_id) and (tenant_id, created_at),
-- but NOT (created_at) alone -> the leftmost-prefix rule.
CREATE INDEX idx_events_tenant_time ON events (tenant_id, created_at);
-- Covering: INCLUDE the selected columns so the query is index-only
-- (no extra trip to the table heap).
CREATE INDEX idx_orders_cover ON orders (user_id) INCLUDE (status, total_cents);
-- Partial: index only the rows you actually query -> smaller and faster.
CREATE INDEX idx_orders_open ON orders (user_id) WHERE status = 'open';05
05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.