Write Index-Friendly SQL
Medium About 15 min Katabench Pro
Hand-written SQL, an indexed timestamp, and a month filter: the shape of your WHERE clause decides whether the planner can use the index.
The full brief is part of Katabench Pro
Pro opens this kata's brief, its starter code and its grader. To see how the track works first, try Customer Order Totals, which is free.
How it is graded
Your LINQ or SQL runs against real PostgreSQL. You see the SQL your code generates on the sample tests and can inspect its execution plan, so you learn when the database did the wrong work.
What it practices
- Sargable predicates
- Write predicates an index can serve: bare columns, ranges and pruned partitions.
- Dates, times and ranges
- Time zones, local day boundaries, month arithmetic and half-open range overlap.
- Query plans
- Read EXPLAIN output to see which access path the planner chose and why.
Related katas
- A Local Month over a UTC Column Medium Pro The report wants a local month, the column stores UTC. Convert the bounds; converting the column costs the index.
- Search One Audit Partition Hard Pro Keep a UTC month range on the partition key so PostgreSQL prunes eleven audit partitions.
- Books by Genre or Language Easy Pro An OR is only as indexable as its weakest branch.
- Cars by Make and Color Easy Pro Why does a planner that happily intersects two indexes settle for one of them here? The statistics are fresh, so the answer is in the WHERE clause.