Apparently, you can "debug" your SQL queries
summary
Claims that SQL can be debugged like application code by reading execution plans and comparing EXPLAIN ANALYZE output (JSON/XML) to find mismatches such as a planned rows = 1 but actual rows = 0, or loops multiplying actual counts; shows how to spot wrong filters, unexpected duplication and large intermediate row counts. Demonstrates a cross‑database prototype called Query Flow that parses plans, visualizes node metrics and highlights the origin of empty or inflated results, and notes the tool is useful but still immature.
AI-written summary · about
chapters (13)
- 0:00intro
- 0:21preface
- 2:18identify flaws in queries is tough
- 3:12buzzword alert! democratization of execution plans
- 3:36query execution flow
- 4:22let's explain explain
- 5:32explain anatomy
- 7:13chat gpt
- 9:46example: empty results
- 11:31aren't there easier ways?
- 12:53query flow
- 16:07pros and cons
- 17:06optimistic future
related talks
52mUnderstanding PostgreSQL Query Plans (aka EXPLAIN)
47mDebugging active queries...
20mLevel up your SQL skills as a developer
44mDebugging your PL/pgSQL code
40mLevel-up Your ActiveRecord Skills: Learn SQL!
50mHow SQL Databases Come up with Algorithms that You Would Have Never Dreamed Of
49mHow to Conduct a Transact-SQL Code Review
32mBecause SQL is everywhere but you don't want to use it