Never Touch the Table
Hard About 30 min Katabench Pro
Ask only for what a covering index already carries so the plan becomes an index-only scan instead of a heap visit per row.
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
- Covering indexes
- Serve a query from the index alone with an index-only scan.
- Query plans
- Read EXPLAIN output to see which access path the planner chose and why.
Related katas
- The CTE That Got Inlined Hard Pro A campaign report scores every listing with an expensive text match and joins the sales in, and the plan runs the scoring once per sales line instead of once per product.
- Search One Audit Partition Hard Pro Keep a UTC month range on the partition key so PostgreSQL prunes eleven audit partitions.
- The Last Calls of the Month Medium Pro The WHERE clause is already perfect and the plan still reads four thousand rows to hand back ten. Graded on the query plan.
- Issues for a Repo Medium Pro The repo slug never leaves your process, so Postgres is asked for two whole tables and obliges.