The CTE That Got Inlined
Hard About 30 min Katabench 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.
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
- Common table expressions
- Name intermediate results with WITH, and know when a CTE is inlined or materialized.
- Query plans
- Read EXPLAIN output to see which access path the planner chose and why.
Do these first
Related katas
- Never Touch the Table Hard 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.
- Enforce an Ordered Conversion Funnel Hard Pro Carry each visitor's next valid timestamp through a campaign funnel without mixing or reordering events.
- 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.